If an operation that comprise of playbook execution gets triggered
while another playbook is running for the same subcloud, the playbook
abortion detection mechanism will fail. Because it's not good to run
two playbooks at the same time, this commit limits this possibility
if any of the deploy_status, backup_status or prestage_status are
in progress.
Test plan:
- PASS: Verify subcloud-backup create, subcloud-backup delete,
subcloud-backup restore, network reconfiguration,
subcloud renaming and subcloud deploy config are mutually
exclusive (i.e, only one of these operations can be executed
at a time).
- PASS: Run subcloud-backup create successfully.
- PASS: Run subcloud-backup delete successfully.
- PASS: Run subcloud-backup restore successfully.
- PASS: Run subcloud network reconfiguration successfully.
- PASS: Run subcloud renaming successfully.
- PASS: Run subcloud deploy config successfully.
- PASS: Run standalone subcloud prestage successfully.
- PASS: Run subcloud prestage strategy successfully.
Closes-bug: 2141319
Change-Id: I28165503f4413d3adb04e899e24524e385381e03
Signed-off-by: Victor Romano <victor.gluzromano@windriver.com>
66ffa6cc93