Not able to cleanup the device as it is referred to a internal service: NSO Access info: 172.23.92.238 [ admin/Cwork123! ]admin@ncs> show zombies % No entries found.admin@ncs> confEntering configuration mode privateadmin@ncs% delete devices device R1admin@ncs% commitAborted: illegal reference 'core-fp-delete-shutdown-service R1 GigabitEthernet 0/0/0/3 device'admin@ncs% run show all devices detailscommit-queue {  completed {    queue-item 1648635163377 {      when        2022-03-30T10:12:55.667022+00:00;      status       failed;      devices      [ R1 R10 ];      completed     [ R10 ];      failed R1 {        reason "External error in the NED implementation for device R1: Mon Apr 4 07:29:39.982 UTC% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below.interface GigabitEthernet0/0/0/3 l2transport!!% Subinterface or Layer 2 configuration conflicts with existing configuration, or configuration in this commit: Cannot configure an interface as L2 when L3 configuration exists !!end";      }      completed-services [ /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service /cisco-flat-L2vpn-fp:flat-L2vpn /core-fp-delete-tag-service:core-fp-delete-shutdown-service /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service ];      failed-services  [ /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service /core-fp-delete-tag-service:core-fp-delete-shutdown-service ];    }    queue-item 1648656408733 {      when        2022-03-30T16:07:00.793551+00:00;      status       completed;      devices      [ R1 R10 ];      completed     [ R1 R10 ];      completed-services [ /cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service[cisco-flat-L2vpn-fp-internal-local-site:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'][cisco-flat-L2vpn-fp-internal-local-site:pe='R1'] /cisco-flat-L2vpn-fp-internal-remote-site:flat-L2vpn-internal-remote-site-service[cisco-flat-L2vpn-fp-internal-remote-site:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'][cisco-flat-L2vpn-fp-internal-remote-site:pe='R10'] /cisco-flat-L2vpn-fp:flat-L2vpn[cisco-flat-L2vpn-fp:name='L2NM-L2vpn_tldp_R1_R10_dot1q-internal'] /core-fp-delete-tag-service:core-fp-delete-shutdown-service[core-fp-delete-tag-service:device='R1'][core-fp-delete-tag-service:if-type='GigabitEthernet'][core-fp-delete-tag-service:if-id='0/0/0/3'] /core-fp-delete-tag-service:core-fp-delete-shutdown-service[core-fp-delete-tag-service:device='R10'][core-fp-delete-tag-service:if-type='GigabitEthernet'][core-fp-delete-tag-service:if-id='0/0/0/3'] /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service[l2vpn-ntw:vpn-id='L2vpn_tldp_R1_R10_dot1q'] ];    }  }}admin@ncs% 
Hello Shanmugavel,I would need a bit more context on this issue to RCA.But from your audit logs, I can assume that this was part of an automation run as I see the following unsupported operations:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java"><INFO> 30-Mar-2022::18:10:31.649 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:31.657 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:31.973 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:31.974 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.288 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.289 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.573 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.574 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:32.882 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:32.882 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.176 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.177 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.509 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.510 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:33.793 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:33.794 nso1 ncs[32303]: audit user: admin/561699 CLI done<INFO> 30-Mar-2022::18:10:34.078 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:34.078 nso1 ncs[32303]: audit user: admin/561699 CLI aborted<INFO> 30-Mar-2022::18:10:34.090 nso1 ncs[32303]: audit user: admin/561699 CLI <INFO> 30-Mar-2022::18:10:34.096 nso1 ncs[32303]: audit user: admin/561699 CLI done</pre></div></div>Again, I would like to strongly emphasize, deleting L2NM and Flat L2VPN in a single transaction is .This is likely why you are experiencing remaining artifacts from core-fp-delete-tag-service.Please reopen another ticket if you are able to reproduce this without executing unsupported operations. We will not spend more time debugging undefined behavior due to unsupported operations. This ticket will be junked unless proven that error is not caused by the conflicting delete.For more context on this, please refer to the following JSD ticket : Thanks,Isaac KimUnsupported operation : delete IETF L2NM and Flat L2 in single transaction.ok, Agree it is not supported operation, we will update the steps in automation but we are looking for the recovery steps here nowHello Shanmugavel,core-fp-delete-tag-service is a fully hidden servicepoint. It cannot be deleted unless with ncs_load commands which must be tailored specifically for your setup.We will not spend more time on these unsupported issues. I am very sorry. Our developer time is very valuable and we are rushing to meet our own deadlines. Please reinstall and ensure you are following our guidelines.Thanks,Isaac Kimthis will be the response "we will not spend time in giving the solution or workaround" when any customer get into issue like this? Take this as a negative case and give us a solution Hello Shanmugavel,We have given a fair warning here : Just like this ticket, we will not resolve your setup because you have executed unsupported operations as part of automation, even when we have given a warning as referenced in above ticket.If you feel like this response is unjustified, please escalate the issue with your manager.Thanks,Isaac Kim