Fix the validation of CPVMs states in multiple zones#13021
Conversation
…rImpl.java Co-authored-by: Bernardo De Marco Gonçalves <bernardomg2004@gmail.com>
|
@blueorangutan package |
|
@winterhazel a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17825 |
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-16111)
|
|
@DaanHoogland, Could you run the tests again? |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian Build Failed (tid-16165) |
|
@weizhouapache ,Could you run the tests again? |
|
[SF] Trillian test result (tid-16178) |

Description
Currently, during the deployment of CPVMs, CloudStack validates whether there are already CPVMs in the
StartingorStoppingstate in the environment, in order to avoid duplicate provisioning. However, this operation does not filter for zones. Therefore, if there is more than one zone in the environment, and in one of these zones there is a CPVM in one of these states, the CPVMs of other zones will not be created.Changes were made to consider only the zone in which the CPVM will be created.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
In an environment with two configured zones,
zn-01andzn-02, I started thezn-01and waited for its system VMs to start while zonezn-02was deactivated. After the system VMs in zonezn-01were in theRunningstate, I changed their states toStartingin the database and activated zonezn-02. I went to the system VMs tab and observed that the system VMs inzn-02were being created while those in zonezn-01were in theStartingstate.