BryanMLima opened a new pull request, #8611: URL: https://github.com/apache/cloudstack/pull/8611
### Description This PR fixes a scenario where if the first cluster verified by ACS does not have any compatible hosts, an exception is thrown, ignoring the verification of possible compatible hosts in other clusters. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI ### Feature/Enhancement Scale or Bug Severity #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [x] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? - Cluster 1: Host A - Cluster 2: Host B Using the environment above, I added the flexible host tag `false` to Host A, and tried to deploy a VM; which would always result on an incompatible host for Cluster 1. Prior to this patch, the `CloudRuntimeException` is thrown with the message `No suitable host found for vm [...].` and Host B is not verified. After applying this patch, the message `No suitable host found for VM [%s] in %s.` is still logged, however, Host B is verified for compatibility and the VM is deployed as expected. #### How did you try to break this feature and the system with this change? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
