Fix VM migration with attached ISO#13330
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #13330 +/- ##
============================================
- Coverage 18.10% 18.10% -0.01%
+ Complexity 16752 16751 -1
============================================
Files 6037 6037
Lines 542796 542806 +10
Branches 66456 66457 +1
============================================
- Hits 98291 98278 -13
- Misses 433460 433482 +22
- Partials 11045 11046 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@hsato03 a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18138 |
|
@hsato03 |
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?