Pre-check flaw fails orchestrated subcloud upgrade retry
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Tee Ngo |
Bug Description
Brief Description
-----------------
The current pre-check logic does not handle the scenario in which upgrading simplex step had failed before the subcloud host was shutdown for remote install in the previous orchestrated upgrade attempt.
The issue was observed during DC upgrade test from 20.06 to 20.12 load with the bug described in https:/
Severity
--------
Major
Steps to Reproduce
------------------
Perform system upgrade from 20.06 (stx4.0) to 20.12 (Nov. 19th, 2020 master load or older) of a distributed cloud.
The bug in the install playbook will cause the upgrading simplex step to fail before the subcloud is reinstalled.
After resolving the issue that caused the failure by either correcting the task to copy default-
Expected Behavior
------------------
Orchestrated subcloud upgrade completes successfully
Actual Behavior
----------------
During the upgrade try, pre-check step to fails health-check due to management affecting alarms (host is locked & upgrade in progress).
Reproducibility
---------------
Reproducible
System Configuration
-------
Distributed Cloud
Branch/Pull Time/Commit
-------
Nov. 17th, 2020 load
Last Pass
---------
Unsure if distributed cloud upgrade from 20.06 -> 20.12 has been officially verified by the test team before.
Timestamp/Logs
--------------
Test Activity
-------------
Developer Testing
Workaround
----------
Log into the subcloud, abort the upgrade, unlock the host and retry the orchestrated subcloud upgrade.
tags: | added: stx.5.0 stx.update |
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
importance: | Undecided → Medium |
https:/ /review. opendev. org/c/starlingx /distcloud/ +/763474