Error recovery Action for slice sync-to/sync-from: 1. Create a slice contains PE-B as one of the SDPs2. Make PE-B out of sync.3. Edit the slice and commit to make the provisioning status = Failed4. Do "Check-Sync" action from transport slice table from CNC UI5. Do "Sync-to" action from transport slice table from CNC UI  It returns "success": false (screenshot attached for more detail)  But the provisioning status for the slice changed from Failed to Successful.   Question 1: Should the Sync-to response be "success": true?6. Check audit log on NSO under /var/log/audit   Question 2: I do not see either "check-sync" or "sync-to" action in audit.log. In order NSO release, we were able to validate the NSO action in audit.log. Is there changes in 6.0?  Question 3: is /var/log/audit the correct location for nso audit.log?
Hi Crystal,1 : Please refer to the following Error Recovery Procedure . As out-of-sync is considered as a Persistent Failure , this will require manual intervention from the user to correct itself. Please refer to steps under Persistent Update Failure Recovery Flow.2 ; 3 : Please find the logs under /opt/log/ncsRegards,Nishad SubairHi Nishad,/opt/log/ncs does not seem to exist. Can you confirm the audit.log location again?# cd /opt/log/ncs-bash: cd: /opt/log/ncs: No such file or directoryThanks.-CrystalHi Crystal,As discussed , the latest audit logs are available under /var/log/ncs after the ncs restart.Please verify.Thanks,Nishad Subair.Hi Nishad,I am able to see the audit.log under /var/log/ncs after the ncs restart. From the chat, I understand "you don't see the most current log due to linux log rotation setting if the ncs is running since some days.". Is there any config change can be done to make the most current log visible instead of restart ncs?Thanks.-CrystalHi Crystal,In some cases , once the logs are rotated, NSO logging is not resumed until you either restart NSO or reload NSO.This is default behavior.You can check more on log rotate configs.Thanks And Regards,Nishad Subair.Here are some more observations in the audit log while make the NSO error recovery request from CNC:1. Actions show in audit.log Check-sync Re-deployReactive-Re-deployClean-up2. Actions NOT show in audit.logSync-toSync-from( as you stated in the chat, sync happens internally and in that case you might not be able to see sync action in log)3. Actions show partial info.Re-deploy dry run: in the log see "re-deploy" but no "dry run""INFO> 13-Sep-2023::00:17:52.023 nso-193 ncs: audit user: root/1221731 RESTCONF: request with https: POST /restconf/data/ietf-network-slice-service:network-slice-services/slice-service=Test-L3-106/re-deploy HTTP/1.1 trace-id=87e67403-99c5-40f9-9467-2326a5aac83d"Question: Should #3 log "re-deploy dry run" in the audit.log because from user's point of view, it is a different action that user request. If we use the same string, it is harder to trace based on the current audit.log.Hi Crystal,Regarding the Question #3 :dry-run is POST data in the redeploy request and post data would not be logged in audit log.Thanks And Regards,Nishad Subair.Hi Crystal ,As discussed , marking the ticket Done.Regards,Nishad Subair.