SadiJr opened a new pull request #5774: URL: https://github.com/apache/cloudstack/pull/5774
### Description Using the VMWare hypervisor, and with Veeam integration enabled, when a VM is assigned to a Backup Offering, ACS executes an operation to clone the Veeam job of that Backup Offering. However, instead of using the Backup Offering specific repository, currently ACS uses the first repository found on Veeam, which can cause problems for users who have more than one repository. This PR intends to fix this behavior. ### 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) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [x] Minor - [ ] Trivial ### How Has This Been Tested? It was tested in a local laboratory, with 2 Veeam repositories: - I assigned two VMs to two Backup Offerings, one for each repository; - The two jobs were created in the same repository, and it should be one for each. This happened because ACS is using the first repository it finds; - With this changes, I repeated the test in the same environment; - Now the jobs are being cloned in the correctly repositories. -- 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]
