SadiJr opened a new pull request #5903: URL: https://github.com/apache/cloudstack/pull/5903
### Description When assigning a VM to a Backup Offering, the information of the VM being attached to a Backup Offering is being saved in the DB before performing the assignment operation in Veeam. Therefore, if any error occurs in Veeam, no rollback is performed, which creates an inconsistency in the DB. ### 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 #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [x] Minor - [ ] Trivial ### How Has This Been Tested? It was tested in a local lab: 1. I created a new Backup Offering; 2. I shutdown the Veeam server (to simulate a problem in Veeam); 2. I tried to assign a VM to this new Backup Offering; 3. Before, an error occurred during the VM assignment process, but since the VM was already assigned to the Backup Offering in DB, it was necessary to remove this VM from the backup offering and try the assign again. 4. With this PR, this behavior is fixed. -- 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]
