While deleting the devices from NSO, getting this error "illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/4 device'": Though there are no zombies in NSO and when we try to delete the devices from NSO , get this error " "illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/4 device'"NSO logs - /auto/ncahi/Users/kbhateja/cw/data_042822_123350.tgz
Hi, KritikaI looked the logs but still don't see any root cause to this issue. Wondering there is service that referred to this device and then you delete the devices?Can you provide the steps that cause this issue?Thanks,LinhHi Linh,The steps that we are doing is - 1. Creating CNC policy (SR, L3VPN)2. Updating the policy created in step-1.3. Deleting the policy.Now sometimes in step-3 , we get the zombies created on NSO. The created zombies are cleaned by re-deploy, resurrect or cleanup command.Later on when we try to delete the devices from NSO , the error "illegal reference 'core-fp-delete-shutdown-service R1 Gigabit Ethernet 0/0/0/4 device'" is seen. Thanks,KritikaAlso attaching the configs that are pushed to the device while creation of policy. Hi Kritika,You created two services in step 1 (SR-Policy and L3VPN) and step 3 you ONLY delete one service which is SR-Policy. L3VPN service is still exist and then you delete devices. NSO CDB still has dangling reference to interface GigabitEthernet 0/0/0/4 which defined in L3VPN service. You should delete L3VPN service before deleting devices. The best practice is when deleting devices, you should do a commit dry-run to see if there is still reference to devices from some services. If there is then you go back and delete then service first then delete the devicesSo it seems the issue occurs when improper action is performed.Thanks,LinhHi Linh,Actually we are creating a policy and deleting it before creating another policy.Also we are making sure to delete all policies and clean the zombies before deleting the devices from NSO but still hitting the issue.Thanks,KritikaHi Kritika,Please try do reproduce this issue again with proper steps. If it still happens then we could have webex to debug it.Thanks,Linh