Symptom
Commit operation for a configuration change did not get implemented or complete.
No error message is seen in the logs but a commit was done but was not successful.
Commit can be verified to be issued via "show cli history detail" or TACACS logs.
Conditions
Mostly seen when a user is running an automation script to make configuration changes in bulk on the XR/LNT Platforms
Workaround
If using automation tools, please ensure the script waits for a router prompt before moving to the next operation or ensure that the session has a large timeout. Perhaps between 3 to 5 minutes.
Further Problem Description
This problem is normally not seen when a manual commit is done as the user should see below on the screen when a commit is issued. However, a script may not wait for below and try to move to the next action with their automation tools or exit the session. If the session exits before the database consolidation is done, the commit will not be successful. If the session stays active while the database consolidation is done, the commit will be successful.
#commit
Fri Sep 15 14:39:03.490 UTC
Loading Rollback Changes.
Loaded Rollback Changes in 1 sec
Committing.System configuration operation in progress: Commit database consolidation.
Please wait or use control-c to cancel this operation.........................................
System configuration operation complete, commit proceeding
If you suspect to be hitting this anomaly and require further investigation, please capture below
and open a TAC case up
show configuration history rebase
show cfgmgr commitdb
show tech-support cfgmgr
show tech-support parser
TACACS logs if show cli history detail wrapped
