JoaoJandre opened a new pull request, #8952: URL: https://github.com/apache/cloudstack/pull/8952
### Description Using KVM as the hypervisor, when migrating a VM that has volumes on NFS storage, if any volume of it is migrated, all volumes that are on NFS must be migrated, otherwise, the migration will fail with the error `unable to execute QEMU command 'block- export-add': Block node is read-only`. This situation occurs because, during the migration of VMs with volumes, the ACS does not inform which volumes should be migrated, causing Libvirt to assume that they will all be migrated, even if their path does not change, leading the hypervisor to try to overwrite the volumes of the VM during migration, resulting in the aforementioned error. The use of the Libvirt migration API has been refactored so that ACS reports which volumes should be migrated. ### 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 #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [X] Major - [ ] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? <!-- Please describe in detail how you tested your changes. --> <!-- Include details of your testing environment, and the tests you ran to --> #### How did you try to break this feature and the system with this change? <!-- see how your change affects other areas of the code, etc. --> <!-- Please read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) document --> -- 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]
