Description of problem: The migrated VM is powered off on the target side once the source VM was off when migration started. Though the source VM turned on during warm migration, before the cutover time Version-Release number of selected component (if applicable): mtv-operator-bundle-container-2.0.0-8 iib 72981 How reproducible: 100% Steps to Reproduce: 1. Power off the source VM 2. Warm migrate it 3. During migration, before the cutover time, turn on the source VM Actual results: When warm migration has succeeded the target VM is powered off Expected results: When warm migration has succeeded the target VM is powered on Additional info:
@slucidi do you think you have enough time to fix this in MTV 2.0.0.
The problem is in VMIO, not MTV. Adjusting the product/component.
The fix should be in build hco-bundle-registry-container-v2.6.3-9.
v2.6.3-16 - failed The vm was turned off.
The source vm was turned off when the plan started and was turned on after a few pre-copies before cutover. The destination vm was not turned on.
Amos, could you please share the full yaml of the VirtualMachineImport resource that was created for that VM? Thank you!
We're too late for 2.6.3. Re-targeting to 2.6.4.
It's probable that the fix was shipped in 2.6.4. Would you mind trying to reproduce it with 2.6.4?
2.6.4 doesn't include any bug fixes, just some annotations to allow direct version upgrades from certain 2.5.z releases to 2.6.4. I am changing the target release to 2.6.5 so that you can check if it has been fixed in that version, if not the next one will be 2.6.6.
https://github.com/konveyor/forklift-controller/pull/291
The issue is reproducible with CVN 4.8.1-17, MTV 2.1.0-44 The destination VM is not powered on at the end of warm migration in both cases: 1. Source VM was on during the whole migration 2. Source VM was off and turned on before cutover Moving to ASSIGNED
Can you please verify with hco-bundle-registry-container-v4.8.2-10 ?
Hi @slucidi, Though this issue looks like it was fixed, there are 2 strange behaviors in warm migration: 1. Once a warm migration is started - I can see under VMware tasks: "Power On virtual machine"/"Power Off virtual machine", depends on the source VM's power state, On/Off accordingly. 2. Once the migration is done and I delete the vmimport CR - if the source VM was On during migration --> the source VM is powered on and only at this point the snapshots are removed. For source VM that was Off during migration - the snapshots are removed as expected, at the end of the warm migration Tested with: CNV-4.8.2-12 MTV-2.1.0-53
(In reply to Maayan Hadasi from comment #14) > Hi @slucidi, > > 1. Once a warm migration is started - I can see under VMware tasks: "Power > On virtual machine"/"Power Off virtual machine", > depends on the source VM's power state, On/Off accordingly. I don't know what was changed in the meantime, but I cannot reproduce this one, after seeing it so many times.
I believe this confirms #2 in Comment 14 was introduced in 4.8.2-12: - in 4.8.2-5 the snapshots are deleted once the VMIO import is completed. - in 4.8.2-12 the snapshots are only removed after deleting VMIO CRs (I also turned on the source VM before deleting the CRs, but the snapshots were only removed after deleting the VMIO CRs).
(In reply to Amos Mastbaum from comment #16) > I believe this confirms #2 in Comment 14 was introduced in 4.8.2-12: > > - in 4.8.2-5 the snapshots are deleted once the VMIO import is completed. > - in 4.8.2-12 the snapshots are only removed after deleting VMIO CRs (I also > turned on the source VM before deleting the CRs, but the snapshots were only > removed after deleting the VMIO CRs). same behaviour when the source VM remains turned off.not related to the source VM state
Two regression BZs have been filed: Bug 2001270 - [VMIO] [Warm from Vmware] Snapshot files are not deleted after Succesfull Import Bug 2001281 - [VMIO] [Warm from VMware] Source VM should not be turned ON if vmio import is removed Thanks Amos. Moving this issue to VERIFIED
Verified as fixed. Versions: CNV 4.8.2-12 iib 104410 MTV 2.1.0-53 iib 99664
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.8.2 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3598