3093104db0

After upgrading the second controller on a Standard config and rolling back a software upgrade on 22.12, the current upgrade abort procedure broke the Ceph monitor quorum resulting in blocked operations to the Ceph cluster. During a platform upgrade of a standard controller deployment, two of three Ceph monitors are required to be unlocked/enabled to maintain a Ceph quorum and provide uninterrupted access to persistent storage. The current procedure and semantic checks required the operator to lock the 3rd monitor on a worker while locking and rolling back the software on one of the active controllers. This left only one monitor active and the Ceph monitors without a an active quorum Another problem was that ceph on controller-1 was being turned off and not turned back on. The change is on the semantic check to make sure that there doesn't need to lock the host which has a monitor and that ceph on controller-1 is up during the entire process of rolling-back on controller-0. Test Plan: Pass: Install Standard 21.12 Patch 9, upgrade to 22.12 make the changes and rollback the upgrade. Pass: Install Storage 21.12 Patch 9, upgrade to 22.12 make the changes and rollback the upgrade. Closes-Bug: 2022964 Signed-off-by: Luiz Felipe Kina <LuizFelipe.EiskeKina@windriver.com> Change-Id: I607a0b2bbf2fa847e8b76425ea5f940be3a81577
Description
Languages
Python
97.6%
Shell
2%
CSS
0.2%