Any chance you misplaced one of the NEDs, and it's missing from the packages directory?
If you have a CLI device configured in NSO, then it's holding a reference to the NED.
If you try to reload packages while the NED is not there, then this reference cannot exist anymore, as the NED is not there anymore. As the ned-id parameter is mandatory when you set the device type to CLI, then you are essentially trying to create an illegal state in CDB, and this is why reload fails.
If you wanted this NED removed, then you'll have to remove all devices configured to use this NED before reloading packages.
NSO Developer Days U.S. is a virtual live event for all of you!
If you have not yet signed up and need 5 more good reasons to attend you should read this blog
Do you want to share your developer experience at future events or have ideas...
I am the NSO Technical Evangelist in the NSO BU. I have started a series I am calling "Learn by Doing", which I take one topic to learn and one use case (as simple as possible, and as focused as possible) and create a repo with some simple explanation tha...
We officially have NSO as a Cisco Ansible collection, aligning to the new way Ansible handles non-core modules:
If you have issues or pull requests you can open them on the following collection repo:
Save the Date for the virtual NSO Developer Days event in APJC (Singapore time)! More information including the registration link with the agenda will be provided closer to the event date.