SR-TE Service cleanup via UI gets stuck in in-progress state: SR-TE Service cleanup via UI gets stuck in in-progress stateIve saved the NSO logs in the below server. Server:172.28.122.102 temp1/Cwork123!$ ls -ltrtotal 1940592-rwxrwxrwx 1 temp1 temp1 131378022 Jun 8 19:52 data_060822_224554.tgz <-CFS-rwxrwxrwx 1 temp1 temp1 946363052 Jun 8 19:54 data_060822_224847.tgz <-RFS-1-rwxrwxrwx 1 temp1 temp1 909420360 Jun 8 20:01 data_060822_225322.tgz <-RFS-2-rwxrwxrwx 1 temp1 temp1 684909909 Jun 8 22:18 showtech_capp-aa_all_20220609050836.tar.gz-rwxrwxrwx 1 temp1 temp1 644942619 Jun 8 22:33 showtech_capp-cat_all_20220609051816.tar.gz$ pwd/tmp/reg7_policy_cleanup$Ive removed the zombie using resurrect, but service is still in in-progress state. Issue seen in both #209 and #214.admin@ncs> request zombies service /sr-te/cisco-sr-te-cfp-sr-policies-internal:policies/policy resurrectresult trueadmin@ncs> show zombie% No entries found.admin@ncs>admin@ncs> show configuration | display set | match 9066admin@ncs>
 Hi Joseph,First thing to note is that zombie resurrect is not a supported action for TSDN CFPs. Second thing to note is that zombie resurrect will restore service state from the zombie itself, so if you see the service back in provisioning state, that is what resurrect is intended to do.Also, I cannot find the logs on your server. Could you provide the absolute path to logs?Could you also detail the steps you took before the cleanup action?Thanks,Isaac Kimzombie resurrect was performed after the clean-up had failed (got stuck in in-progress). So how do we remove this zombie?Could you also detail the steps you took before the cleanup action?Step1 : Create the service via UI using l2vpn_R1_R10_srpolicy_tldp_dot1q.iniStep2 : Start Basic monitoring and then stop monitoringStep3 : Perform clean-up via UI Could you provide the absolute path to logs?$ pwd/tmp/reg7_policy_cleanup$Hi Joseph,From your steps, it seems like you executed cleanup action without first deleting service. This is not a supported flow for TSDN. Cleanup action should only be executed as a last resort option to clear a failed delete service as stated in our documentation. As such, delete should always precede cleanup, otherwise you will face race conditions such as leftover artifacts.Please try the following steps:1. Delete service + commit2. Check for zombies, if there are stuck zombies continue to next step3. Execute cleanup action targeting serviceHi Joseph, we have discussed few recovery options via Webex chat. I believe we have been able to address your issue for this JSD ticket. If there is no reply in next few days, I will close this ticket.Thanks,Isaac Kim