Hide Forgot
Description of problem: After migration from 3.4 to 3.6, the .vv spec file for VM is not updated to the new specs Version-Release number of selected component (if applicable): 3.4 DC to 3.6.5 How reproducible: Have not created a reproducer, but will repeat on customers hardware/environment. Steps to Reproduce: 1. Create 3.4 DC with rhevm managment/display network. 2. Create VM on the 3.4 envi 3. Create a new 3.6.5 cluster with ovirtmgmt management/display network 4. Add rhevm network to the 3.6.5 for the migration 5. Migrate the VM from 3.4 to 3.6.5 6. After the migration, the VM still has the specs from the original .vv that say that the management/display comes from rhevm instead of from ovirtmgmt Actual results: .vv file for test VM points to rhevm network Expected results: .vv file for test VM points to ovirtmgmt Additional info:
Can you please provide more details for step 5? How exatly did tou do that, shutdown and edit VM and change its cluster?
inter-cluster migration is not supported for anything else than 3.5 el6 to el7 migration. It's not supposed to change anything and once the VM is shut down it won't be able to start again on those host. You need to move the VM when it's shutdown to the new cluster, which will change configuration (network, machine type, etc)
after further investigation we found out that editing cluster level is not blocked when VMs are running. Several things are checked by bug 1298487 but this basic case is not applied. We need to check any non-Down state and block on it
(In reply to Michal Skrivanek from comment #4) > after further investigation we found out that editing cluster level is not > blocked when VMs are running. Several things are checked by bug 1298487 but > this basic case is not applied. We need to check any non-Down state and > block on it AFAIR, we REALLY do not want to enforce all VMs to be down when changing cluster level - was that ever a requirement?
Verified on: oVirt Engine Version: 4.1.0-0.0.master.20160605051229.gitb398fa2.el7.centos Verification steps: 1. Create a DC with 3.6 compatibility version 2. Add a host with 3.6 compatibility version 3. Create and run vm 4. Try to edit the 3.6 compatibility version in cluster from 3.6 to 4.0 Result : 'shut down all vm before changing the cluster level'
Removing the doc text since this feature is changed by #1356027 and especially gerrit 61079 . Recent behavior: Cluster version change is allowed in Cluster Edit dialog even if there are running/suspended VMs. These not-down VMs are marked by NextRun configuration icon. VM Custom compatibility level is set to original cluster version until shut down+restart.
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, 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://rhn.redhat.com/errata/RHEA-2016-1743.html