Description of problem:
VMs with payload device (sysprep, cloud init) can no longer properly migrate if
clusters <= 4.1 are upgraded with Vdsm >= 4.2, while still retaining the old clusterLevel.
Version-Release number of selected component (if applicable):
Any Vdsm >= 4.2 in cluster <= 4.1
Steps to Reproduce:
1. Prepare a <= 4.1 oVirt environment, upgrade Vdsm to 4.2.2 in a cluster
2. Run a VM with either sysprep or cloud-init
3. Suspend the VM
4. Try to migrate (or suspend again) the same VM
The last migration/suspension will fail
Migration/suspension should succeed as usual
VMs without payload devices are not affected.
Vdsm fail to properly store the information needed to rebuild the payload device past the first time, so after the first time the VM goes away (e.g. suspension, migration or even Vdsm restart), it can no longer rebuild it, and the corresponding VM device (e.g. cdrom) will be dangling, leading to migration failures.
no doc_text: this should "just work" and should not have user-visible consequences. Aka the behaviour should not have changed.
1. Create VM
2. Run VM with cloud init on 4.1 host in 4.1 cluster on rhevm 4.2.3
3. Check that VM has payload on the host.
CASE 1: Migrate to 4.2 host
CASE 2: Suspend VM and Resume the VM on 4.2 host. (host on cluster 4.1)
Payload exist on 4.2 host for both cases
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.