Closed vsoaresf closed 2 years ago
It seems that any failed reply originates a core dump. Substituting the YFilter.delete by YFilter.remove avoids the bad reply from the device, the workaround for my case.
ydk.errors.YServiceProviderError: <?xml version="1.0"?>
application data-missing error ns1:router-static/ns1:default-vrf/ns1:address-family/ns1:vrfipv4/ns1:vrf-unicast/ns1:vrf-prefixes/ns1:vrf-prefix[prefix = '192.168.30.32' and prefix-length = '32']
terminate called after throwing an instance of 'pybind11::error_already_set' what(): NameError: name 'open' is not defined
At: /usr/lib/python3.6/logging/init.py(1061): _open /usr/lib/python3.6/logging/init.py(1071): emit /usr/lib/python3.6/logging/init.py(867): handle /usr/lib/python3.6/logging/init.py(1516): callHandlers /usr/lib/python3.6/logging/init.py(1454): handle /usr/lib/python3.6/logging/init.py(1444): _log /usr/lib/python3.6/logging/init.py(1308): info
Aborted (core dumped)
Issue tracker is ONLY used for reporting bugs. Please use the YDK Community for any support issues.
Expected Behavior
All exceptions should be catch and handled in a proper manner
Current Behavior
When an XML RPC call is returned with error the YDK client is not able to handle this exception and core dumps.
Steps to Reproduce
Using the Cisco_IOS_XR_infra_policymgr_cfg try to delete an inexistent policy-map-rule in a given policy-map
Your Script
Logs
Enable logging and post the logs below
System Information
pkg-resources==0.0.0 pybind11==2.4.3 ydk==0.8.4 ydk-models-cisco-ios-xr==6.6.3 ydk-models-ietf==0.1.5.post2
Distributor ID: Ubuntu Release: 18.04 Codename: bionic