-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix migration issue in UserVmManagerImpl.migrateVirtualMachineWithVolume #5288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@blueorangutan package |
|
@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian. SL-JID 788 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I need to hide somewhere, added this with #5030 .
Also, have to check why this smoke tests were not showing failures
Because in test_vm_life_cycle.py,
Created #5289 to add a smoke test for live migrate VM with volume for VMware. |
|
@blueorangutan test matrix |
|
@shwstppr a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm, makes sense
|
Trillian test result (tid-1533)
|
|
Trillian test result (tid-1532)
|
|
Will merge this and the test fix PR and kick test matrix on the health check PR. PR LGTM |
|
Trillian test result (tid-1534)
|
Description
I've upgraded a stage environment from an older 4.16-SNAPSHOT to the current one and found a regression bug at the VM migration.
When calling the
migrateVirtualMachineWithVolume, the followingInvalidParameterValueExceptionis launched:Unsupported hypervisor: KVM for VM migration, we support XenServer/VMware/KVM only.Types of changes
Bug Severity
How Has This Been Tested?
The test was executed on a cluster with KVM nodes.
At the UI, migrate a VM with a Root volume allocated in a local storage. Or, call the API command migrateVirtualMachineWithVolume.