bff2f0aa2f
It is risky to update a subcloud's network if there is an existing vim strategy: the on-going vim strategy triggers lock/unlock/swact can interrupt the ansible-playbook, leaving the subcloud in an un-recoverable state. To prevent this issue, this commit checks the on-going vim strategy, and blocks the further operation if it exists. Test plan: 1. Passed - deploy a DC with this change. 2. Passed - create a kube-rootca-update orchestration against a subcloud, verify the subcloud update with network reconfiguration is blocked by the ongoing strategy, verify the network reconfiguration is not blocked after the strategy applied. 3. Passed - create a system-config-update strategy by updating the addresspool on the subcloud, verify the subcloud update with network reconfiguration is blocked when applying this strategy, verify this operation is not blocked after the strategy applied. Story: 2010722 Task: 49414 Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com> Change-Id: I2c3b824ebbd6766996f3422c681f16d03b6063fa |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| barbican.py | ||
| dcmanager_v1.py | ||
| fm.py | ||
| keystone_v3.py | ||
| patching_v1.py | ||
| peer_site.py | ||
| sdk_platform.py | ||
| software_v1.py | ||
| sysinv_v1.py | ||
| vim.py | ||