AIO-DX: controller-1 failed after host-downgrade and unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Angie Wang |
Bug Description
Brief Description
-----------------
During stx4.0 to stx5.0 upgrade, upgrade abort cannot be completed due to controller-1 can not be unlocked successfully after host-downgrade.
The root cause is cgts-vg is decreased in stx5.0 so new partition and pv are introduced during controller-1's upgrade and sysinv-agent sends the new partition and pv data back to controller-0 which is running stx4.0 so stx4.0 database gets updated with the new partition and pv that causes the unlock failed.
Severity
--------
Major
Steps to Reproduce
------------------
system upgrade-start
system host-lock controller-1
system host-upgrade controller-1
system host-unlock controller-1
system upgrade-abort
system host-lock controller-1
system host-downgrade controller-1
sudo sw-patch host-install controller-1
system host-unlock controller-1
Expected Behavior
------------------
controller-1 is downgraded and unlocked successfully, controller-1 becomes available
Actual Behavior
----------------
controller-1 was downgraded, but after unlock, controller-1 stayed at failed state
Reproducibility
---------------
100% Reproducible
System Configuration
-------
AIO-DX
Last Pass
---------
N/A
Timestamp/Logs
--------------
2021-01-
2021-01-
2021-01-
Test Activity
-------------
Developer Testing
Workaround
----------
None
Changed in starlingx: | |
assignee: | nobody → Angie Wang (angiewang) |
tags: | added: in-r-stx50 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/786724
Review: https:/