After service recreation (delete+create) , service provisioning takes more time - ~5 minutes or more: After service recreation (delete+create) , service provisioning takes more time - ~5 minutes or moreSetup: 10.195.165.76 - admin/Admin*123 - cw-admin/Ovatest123@NSO: 10.195.165.123 - nso123/nso123Service name: bundlencs540
Ajitha reached out with another service (which was deleted and then recreated) taking a long time to get provisioned. When looking into this service, on the NSO it looks like service creation is stalled as there is no lifecycle-state information :<blockquote>admin@ncs>show devices device onc-real-new live-status context connectivity-context connectivity-service 6171500c-923c-4e60-9860-f6b8b947a313 lifecycle-state% No entries found.admin@ncs> show ron uuid-lookupRON MLSERVICE    UUID----------------------------------------------------9903     6171500c-923c-4e60-9860-f6b8b947a313bundlencs540 de1e357f-b208-4f08-ae5d-49bbeeddd27afreta     94baae3e-0b85-48dc-b1cd-fa1c99fc8156</blockquote>The ONC trace does not show any notifications either.Looking into the ONC, the service data shows the following:<blockquote>{   "uuid": "6171500c-923c-4e60-9860-f6b8b947a313",   "name": [    <div class="error"> </div>   ],   "administrative-state": "UNLOCKED"  },</blockquote>This is missing the following info:<blockquote>"operational-state": "ENABLED","lifecycle-state": "INSTALLED"</blockquote>Recommended Ajitha reach out to ONC team for further assistanceAs discussed with Ajitha. The issue is that there is a delay in the lifecycle-state notification from the ONC to the NSO. In the most recent case (service 9903), there was no notification (success or failure) and the service was stalled on the NSO. I suggest reaching out to ONC team for further assistanceDid some more looking into the ONC trace. Copying the relevant ONC notifications with timestamps here. There is ~10 minute delay between the PLANNED and INSTALLED notif from the ONC.<blockquote><<<<in 6-Oct-2021::18:42:42.773 user: admin/274864 thandle 254296 hostname nso123 device onc-real-new session-id=1761<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"      message-id="2"> <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda">  <context xmlns="urn:onf:otcc:yang:tapi-common">   <connectivity-context xmlns="urn:onf:otcc:yang:tapi-connectivity">    <connectivity-service>     <uuid>de1e357f-b208-4f08-ae5d-49bbeeddd27a</uuid>     <lifecycle-state>PLANNED</lifecycle-state>    </connectivity-service>   </connectivity-context>  </context> </data></rpc-reply><<<<in 6-Oct-2021::18:51:11.825 user: admin/275168 thandle 254687 hostname nso123 device onc-real-new session-id=1828<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"      message-id="2"> <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda">  <context xmlns="urn:onf:otcc:yang:tapi-common">   <connectivity-context xmlns="urn:onf:otcc:yang:tapi-connectivity">    <connectivity-service>     <uuid>de1e357f-b208-4f08-ae5d-49bbeeddd27a</uuid>     <lifecycle-state>INSTALLED</lifecycle-state>    </connectivity-service>   </connectivity-context>  </context> </data></rpc-reply></blockquote>As discussed. ONC team to take this forward. 