This commit includes:
1. Rebuild the region one patch cache during the service reload.
2. Ignore the patch in progress alarm as this could be a patch
orchestration retry.
3. Re-create workers if they are cleard after a service restart.
4. Properly handle reboot-required patching in case both system
controller and subcloud patch orchestration is done in one single
strategy.
With these improvement, the patch strategy can continue after a
service reload.
Test plan(passed):
1. Verify successful patch orchestration of an RR patch when both
system controller and subclouds are patched in the same strategy.
2. Induce a 300.005 alarm (mgmt-affecting) in a subcloud, verify
that orchestrated patching fails for that subcloud.
3. Induce a 900.001 alarm by partially apply a patch in a subcloud
beforehand, verify that orchestrated patching completes for that
subcloud.
4. Induce process restart in the middle of a subcloud patch
orchestration, verify that transitional strategy steps are set to
failed and the subclouds still in "initial" state can continue.
5. Induce process restart in the middle of a system controller patch
orchestration, verify that system controller patching can resume and
complete.
Closes-Bug: 1979097
Signed-off-by: Yuxing Jiang<Yuxing.Jiang@windriver.com>
Change-Id: I1b70d14b77c3e1be6301f011baff297502b9108b
29fe24acb3