We see that when we get ned_prepare_cli errors either during service activation or service rollback. That it leaves the the services defined in the CDB database, but it does print us a nice message. With chained services then we have lots of clean up of the CDB to get ready to retest.
Is there a recommended way to capture these errors to try to leave the system in a better state?
In an ncs system-install – is there a recommended way to reset the database? To assit with clean up.
Sometimes these errors do not manifest themselves until we are applying or rolling back these chained services. When we test the services independently we do not have an issue. So they are complexity driven. In our services we have to apply configuration to our STAROS device in multiple services in order to activate the licensing correctly – before configuring the devices. So we use reactive fastmap for this.