After consuming new ONC, provisioning fails : After consuming new ONC, provisioning fails Please see attached .Env Details: NSO: ssh+ UI -> nso552/Public1234!CNC: UI: admin/Public1234!SSH: cw-admin/Public1234!
Hi Yevgeny, the issue you are seeing is due to ONC is missing transmit power in connectivity service output. We will have to wait for ONC to provide a fix.Roberto has provided the workaround:With the build 17.09.2021.CVT.CB4 and by applying the correct Env Variable (updated in wiki page copied below for convenience)On a CW cluster with ONC already deployed, execute on the shell:<ol></ol>This will open up a vi editor.  2. Scroll down to section, 3. the following lines if they are present (added as part of previous workaround):- name: networkholder.optval.activation.active.defaultvalue: ZONE_UNKNOWN- name: networkholder.optval.activation.whatif.defaultvalue: ZONE_UNKNOWN  4. the following lines to workaround the missing Logo params on the device- name: optvalidation.logo_data.mandatoryvalue: "false"  5. Save the file and exit  6. All 3 replicas of onc-pce-service will restart (starting from onc-pce-service-2)  7. Once restarts are complete (may take up to 15 minutes and can be checked with "kubectl get pod | grep onc-pce") ONC usage can resume