Bug 1340345 - Cluster level can be changed while there are running VMs
Summary: Cluster level can be changed while there are running VMs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.0.0
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.7
: 3.6.7.1
Assignee: Marek Libra
QA Contact: sefi litmanovich
URL:
Whiteboard:
Depends On:
Blocks: 1336527 1341023
TreeView+ depends on / blocked
 
Reported: 2016-05-27 06:27 UTC by Michal Skrivanek
Modified: 2016-07-04 12:33 UTC (History)
22 users (show)

Fixed In Version:
Clone Of: 1336527
Environment:
Last Closed: 2016-07-04 12:33:20 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
michal.skrivanek: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 57799 0 None None None 2016-05-27 06:27:10 UTC
oVirt gerrit 58125 0 ovirt-engine-4.0 MERGED webadmin: Forbid cluster version change if a VM is active 2016-05-27 15:02:44 UTC
oVirt gerrit 58245 0 ovirt-engine-3.6 MERGED webadmin: Forbid cluster version change if a VM is active 2016-05-30 13:11:01 UTC
oVirt gerrit 58276 0 ovirt-engine-3.6.7 MERGED webadmin: Forbid cluster version change if a VM is active 2016-05-30 19:46:17 UTC

Description Michal Skrivanek 2016-05-27 06:27:10 UTC 
+++ This bug was initially created as a clone of Bug #1336527 +++

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:

--- Additional comment from Michal Skrivanek on 2016-05-17 16:55:02 CEST ---

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
Comment 1 Michal Skrivanek 2016-06-22 09:45:57 UTC 
see bug 1348907 for possible removal of this restriction
Comment 2 sefi litmanovich 2016-06-22 17:02:04 UTC 
Verified that restrictions are implemented on rhevm-3.6.7.4-0.1.el6.noarch.

1. Created a 3.4 DC.
2. Created a 3.4 cluster.
3. Added rhel 6.6 host with latest 3.4 vdsm.
4. Created a vm and started it on the cluster.
5. Tried to change comparability version of the cluster to 3.5 - cannot change, got the message suggesting to shutdown vm.

Did the same with 3.5 to 3.6.
Note You need to log in before you can comment on or make changes to this bug.