Possible bug in T-SDN FP 5.0 code: Ive found this problem in the RON Brussels lab ( its a Cisco lab).KeyError: '{pe1_Vodafone} not in /ncs:devices/device'Heres my report::: CNC packages in the Lab ::ncs-6.1-cisco-flat-L3vpn-fp-internal-5.0.0.tar.gzncs-6.1-cisco-tsdn-core-fp-common-5.0.0.tar.gzncs-6.1-custom-template-utils-2.0.13.tar.gzncs-6.1-ietf-l3vpn-nm-5.0.0.tar.gz:: NSO Version ::6.1:: Problem ::Error when updating a l3vpn-ntw vpn-services vpn-service:<ERROR> 26-May-2023::10:47:30.877 ietf-l3vpn-nm ncs-dp-51986-ietf-l3vpn-nm:main:10-7-th-774054: - '{pe1_Vodafone} not in /ncs:devices/device'Traceback (most recent call last): File "/opt/ncs/ncs-6.1/src/ncs/pyapi/ncs/application.py", line 875, in wrapper  pl = fn(self, tctx, op, kp, root, proplist) File "/var/opt/ncs/state/packages-in-use/1/core-fp-common/python/core_fp_common/instrumentation.py", line 151, in wrapper_instrument_service  result = func(*args, **kwargs) File "/var/opt/ncs/state/packages-in-use/1/ietf-l3vpn-nm/python/ietf_l3vpn_nm/ietf_l3vpn_nm_nano_plan.py", line 327, in cb_post_modification  device_cq_details = is_cq_enabled(self, root, File "/var/opt/ncs/state/packages-in-use/1/cisco-tsdn-core-fp-common/python/cisco_tsdn_core_fp_common/utils.py", line 229, in is_cq_enabled  get_device_cq_details(root, device_cq_details, devices) File "/var/opt/ncs/state/packages-in-use/1/cisco-tsdn-core-fp-common/python/cisco_tsdn_core_fp_common/utils.py", line 241, in get_device_cq_details  per_device_cq = root.ncs__devices.device.commit_queue.enabled_by_default File "/opt/ncs/ncs-6.1/src/ncs/pyapi/ncs/maagic.py", line 1177, in _<em>getitem</em>_  raise KeyError('%s not in %s' % (keystr, self._path))KeyError: '{pe1_Vodafone} not in /ncs:devices/device':: Investigation ::The device name is pe1 but the code is using the component naming <DEVICE>_<VPN_NETWORK_ACCESS_ID>, pe1_Vodafone in the xpath expression.This happens when doing a CQ flag check in the post modification callback.Image:: Steps to reproduce the problem ::1) Connect to RON Brussels lab ( Its a Cisco lab)ssh ncsadmin@10.48.188.21Cisco!1232) Create a new l3vpn-ntw vpn-services vpn-serviceService Payloadl3vpn-ntw vpn-services vpn-service Vodafonevpn-instance-profiles vpn-instance-profile 1 rd 0:10:1 address-family ipv4  vpn-targets vpn-target 1  route-targets 0:100:100  !  route-target-type both  ! !!vpn-nodes vpn-node pe1 active-vpn-instance-profiles vpn-instance-profile 1 ! vpn-network-accesses vpn-network-access Vodafone_100  interface-id FourHundredGigE0/0/0/1  connection encapsulation type dot1q  connection encapsulation dot1q cvlan-id 100  ip-connection ipv4 local-address 172.16.100.151  ip-connection ipv4 prefix-length 24 !!!3) Try to update the service:l3vpn-ntw vpn-services vpn-service Vodafone vpn-instance-profiles vpn-instance-profile 1 rd 0:10:2
Hi Paulo,This issue is because of the "_" present in the vpn_network_access id. The component in this case becomes "pe1_Vodafone_100". The code is not properly handling the underscore when getting the device name from this component.We already identified the issue internally and have made changes to the code to handle such situations.The updated code would be released as part of .0 release.Thanks,NikhilThe updated code would be released as part of .0 release.