Just a couple of suggestions:
-match these commit-queue settings if not already configured:
ncs# show full-configuration devices global-settings commit-queue | details
devices global-settings commit-queue enabled-by-default false
devices global-settings commit-queue atomic true
devices global-settings commit-queue connection-failure-reconnect-timer 30
devices global-settings commit-queue connection-failure-reconnect-retries unlimited
-Restart NSO instance, perform a ‘devices commit-queue clear’ to clean the entire queue, perform a sync-from, provide check-sync/compare-config outputs, reproduce the issue (please share all this data).
The error alone is vague, but this should provide more clarity to what's going on. The first option are just settings while the second option is more intuitive.
Also, reasons for this issue could be:
1. If a device rejects the proposed change, NSO and the device are now out of sync until any error recovery is performed. Whenever this happens, an NSO alarm (called commit-through-queue-failed) is generated.
2. locked - This queue item is locked and will not be processed until it has been unlocked, see the action /ncs:devices/commit-queue/queue-item/unlock. A locked queue item will block all subsequent queue items which are using any device in the locked queue item.
