Backup & Restore: AIO-DX+worker Controller failed to become active after restore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Stefan Dinescu |
Bug Description
Brief Description
-----------------
In AIO-DX+worker configuration, the active controller failed to become active after restore and unlock.
/var/log/
error with running `drbdadm create-md drbd-pgsql -W--peer-
Severity
--------
Critical: Unable to restore active controller
Steps to Reproduce
------------------
1. Bring up the AIO-DX+worker 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
-------
AIO-DX+worker
Branch/Pull Time/Commit
-------
BUILD_
Test Activity
-------------
Feature Testing
tags: | added: stx.update |
Changed in starlingx: | |
status: | New → Triaged |
assignee: | Senthil Mukundakumar (smukunda) → Ovidiu Poncea (ovidiu.poncea) |
Changed in starlingx: | |
assignee: | Ovidiu Poncea (ovidiu.poncea) → Stefan Dinescu (stefandinescu) |
tags: | added: stx.4.0 |
tags: | removed: stx.cherrypickneeded |
Hi Senthil,
We need more details:
1. The lab that has the issue was on (thanks for the email, it is wp_8_12 and it had IPv6 support)
2. The collect after backup and before the reinstall of controller-0
3. The backup archive
We will do a test on an AIO-DX IPv6 to see if it works & will need a DX+Worker lab in IPv6 mode to restest.