00a3e50e71
The prestage release can be either the previous or current release for
a subcloud. Checking the prestage release individually on thousands of
subclouds is impractical. Therefore, a new column called "prestage
versions" is added to the output of the "dcmanager subcloud list'
command. Besides, decoupling prestage status from deploy status.
Test plan:
PASS: Successful subcloud prestage with specified 22.12 or 23.09
release, and verified the correct "prestage versions" output of
the "dcmanager subcloud list" command.
PASS: Successful prestage strategy with specified 22.12 or 23.09
release, and verified the correct "prestage versions" output of
the "dcmanager subcloud list".
PASS: Verified the "prestage status" at each prestage stage.
PASS: Verified that the 'deploy status' was updated to 'complete' after
upgrading the system controller from version 22.12 to 23.09.
This verification was performed specifically for those subclouds
that had a 'prestage-complete' deploy status with the previous
22.12 system controller. The new columns, "perstage status" and
"prestage versions", were empty after upgrading.
Depends-on:
https://review.opendev.org/c/starlingx/ansible-playbooks/+/904546
Story: 2010611
Task: 49367
Change-Id: Ica65b1e2e8e44b96352e7d45439a2e7a9063f7c9
Signed-off-by: lzhu1 <li.zhu@windriver.com>
|
||
|---|---|---|
| .. | ||
| alarms | ||
| peer-group-associations | ||
| phased-subcloud-deploy | ||
| subcloud-backup | ||
| subcloud-deploy | ||
| subcloud-groups | ||
| subcloud-peer-groups | ||
| subclouds | ||
| sw-update-options | ||
| sw-update-strategy | ||
| system-peers | ||
| root-get-response.json | ||