| 2018-11-14 19:54:44 |
Sai Chakravarthy Alikapati |
description |
The device_import playbook does not onboard interfaces of a device when the fabric delete is still removing config, but the discovery and role assignment still is successful. This happens when the discovery process is started as soon as the delete fabric job exits. The reason is that the playbooks are not able to edit the config on the device in private mode. It is the resultant of overlapping config edits on the devices. Following are the errors observed in the process.
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to open the configuration in private mode: RpcError(severity: warning, bad_element: None, message: warning: changes cannot be committed while 'configure exclusive' is active\nwarning: uncommitted changes will be discarded on exit)"}
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to open the configuration in exclusive mode: LockError(severity: error, bad_element: None, message: configuration database modified)"} |
The device_import playbook does not onboard interfaces of a device when the fabric delete is still removing config, but the discovery and role assignment still is successful. This happens when the discovery process is started as soon as the delete fabric job exits. The reason is that the playbooks are not able to edit the config on the device in private mode. It is the resultant of overlapping config edits on the devices. Following are the errors observed in the process.
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to open the configuration in private mode: RpcError(severity: warning, bad_element: None, message: warning: changes cannot be committed while 'configure exclusive' is active\nwarning: uncommitted changes will be discarded on exit)"}
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to open the configuration in exclusive mode: LockError(severity: error, bad_element: None, message: configuration database modified)"}
Workaround for this issue is that the discovery process should not be started until the delete process is complete. |
|
