You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using KVM, if a VM with an attached ISO is migrated to a host that does not have the path of that ISO mounted, but already has the libvirt storage pool corresponding to that ISO created, an exception is thrown. Therefore, it is not possible to migrate this VM.
Based on this, changes were made to ensure that the path of the ISO attached to the VM will be mounted during the migration.
Types of changes
Breaking change (fix or feature that would cause existing functionality to change)
New feature (non-breaking change which adds functionality)
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
Test (unit or integration test code)
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Major
Minor
Bug Severity
BLOCKER
Critical
Major
Minor
Trivial
Screenshots (if appropriate):
How Has This Been Tested?
I deployed a VM on host A and attached an ISO to it;
I migrated this VM to host B;
I unmounted the ISO directory on host A;
I attempted to migrate the VM to host A.
Without the changes: an error occurred stating that it was not possible to mount the ISO's storage pool and the migration failed.
With the changes: the storage pool was mounted and the migration finished successfully.
How did you try to break this feature and the system with this change?
❌ Patch coverage is 21.42857% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 18.10%. Comparing base (7308dad) to head (427e49c). ⚠️ Report is 1 commits behind head on main.
@hsato03 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.
The reason will be displayed to describe this comment to others. Learn more.
clgtm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Using KVM, if a VM with an attached ISO is migrated to a host that does not have the path of that ISO mounted, but already has the libvirt storage pool corresponding to that ISO created, an exception is thrown. Therefore, it is not possible to migrate this VM.
Based on this, changes were made to ensure that the path of the ISO attached to the VM will be mounted during the migration.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Aand attached an ISO to it;B;A;A.Without the changes: an error occurred stating that it was not possible to mount the ISO's storage pool and the migration failed.
With the changes: the storage pool was mounted and the migration finished successfully.
How did you try to break this feature and the system with this change?