Comment 0 for bug 1850714
Revision history for this message
| Senthil Mukundakumar (smukunda) wrote Backup & Restore: Standby controller failed to come abailable after restore/unlock action in Regular system | #0 |
Brief Description
-----------------
In Regular system Backup & Restore, the active controller did become active after restore (1849379 - verified).
The standby controller after restore and unlock, remain in failed state using 'system host-list'.
[sysadmin@
+----+-
| id | hostname | personality | administrative | operational | availability |
+----+-
| 1 | controller-0 | controller | unlocked | enabled | available |
| 2 | controller-1 | controller | unlocked | disabled | failed |
| 3 | compute-0 | worker | locked | disabled | offline |
| 4 | compute-1 | worker | locked | disabled | offline |
+----+-
Severity
--------
Critical: Unable to restore standby 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
6. Boot standby controller via PXE
7. unlock standby controller
Expected Behavior
------------------
The standby controller should be successfully restored and become available
Actual Behavior
----------------
Standby controller failed to become available after unlock
Reproducibility
---------------
Reproducible
System Configuration
-------
Regular System
Branch/Pull Time/Commit
-------
BUILD_
Test Activity
-------------
Feature Testing