Backup & Restore: Controller failed to become active after restore in Regular system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Ovidiu Poncea |
Bug Description
Brief Description
-----------------
Active controller failed to become active after restore and unlock. It is waiting for sm process.
controller-0:~$ source /etc/platform/
Openstack Admin credentials can only be loaded from the active controller.
Relevant sm logs:
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
Severity
--------
Critical: Unable to restore active controller in Regular system
Steps to Reproduce
------------------
1. Bring up the Regular system system
2. Backup the system using ansible locally
3. Re-install the controller with the same load
4. Restore the active controller
5. Unlock active controller
Expected Behavior
------------------
The active controller should be successfully restored and become active
Actual Behavior
----------------
Active controller failed to become active after unlock
Reproducibility
---------------
Reproducible
System Configuration
-------
Regular System
Branch/Pull Time/Commit
-------
BUILD_
Test Activity
-------------
Feature Testing
Openstack Admin credentials can only be loaded from the active controller.
Error: can only run collect for remote hosts on active controller (reason:35)
stx.3.0 / high priority - B&R is a feature deliverable for stx.3.0