We no longer check for upgrade state during kickstart execution. Moving
forward (beginning this release), upgrades are done via USM, and no
longer involve installation. Therefore there is no longer a need to
check and act on upgrade states during installation.
The upgrade checks are removed, simplifying the code flow in both the
main and miniboot kickstarts.
For remote operation against a subcloud, a kernel argument is added:
'wipe_osds' (default value is true). If false, this will cause the OSDs
to be preserved over install - this is currently used in the restore
use-case, and is controlled by dcmanager.
Test Plan
PASS : install system controller in libvirt (controller-0)
PASS: install inactive controller-1 via pxeboot
PASS: Verify that OSD disk wiping happens when the wipe_osds parameter
is queried from pxecontroller address
For subcloud:
PASS: Install subcloud via sushy
PASS: Install subcloud via sushy, pass in wipe_osds flag. Ensure OSDs
are wiped.
PASS: Verify that OSD disk wiping is triggered during subcloud
remote-install when "wipe_osds: True" is included in
the install_values.
PASS: Verify that OSD disk wiping is skipped during subcloud
remote-install when "wipe_osds" is removed from
the install_values.
PASS: Verify that OSD disk wiping is skipped during a backup
restore, regardless of whether "wipe_osds" exists in
the data_install (this is via the wipe_osds flag).
Closes-Bug: 2091589
Co-authored-by: Kyle MacLeod <kyle.macleod@windriver.com>
Change-Id: Ic68c70fa084cfc3331bc7b05f5dbbf4b3b084a30
Signed-off-by: lzhu1 <li.zhu@windriver.com>
a0f8eb3fc4