Bug 856172

Summary: engine: cannot raise cluster's compatibility level when we have running vm's
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Roy Golan <rgolan>
Status: CLOSED CURRENTRELEASE QA Contact: Ido Begun <ibegun>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.1.0CC: acathrow, alonbl, dyasny, emesika, iheim, lpeer, michal.skrivanek, mkenneth, oramraz, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: si20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 20:07:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log none

Description Dafna Ron 2012-09-11 11:29:49 UTC 
Created attachment 611729 [details]
log

Description of problem:

we are blocked by CanDoAction when trying to raise cluster's compatibility version with running vm's:

Error: Cannot update Cluster and change its compatibility version
if there are running VMs 

this blocks live upgrade. 

Version-Release number of selected component (if applicable):

si17

How reproducible:

100%

Steps to Reproduce:
1. create a 3.0 DC+Cluster+vm's
2. upgrade the vdsm 
3. change compatibility in cluster to 3.1
  
Actual results:

Error: Cannot update Cluster and change its compatibility version
if there are running VMs 

Expected results:

we should be able to raise the cluster's compatibility level

Additional info: engine log
Comment 4 Roy Golan 2012-09-16 04:39:30 UTC 
http://gerrit.ovirt.org/#/c/7987/
Comment 5 Roy Golan 2012-09-16 09:47:13 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=ae50b2dfb8dccac30df4238bda592545bf4d5200
Comment 20 Ido Begun 2012-10-14 12:25:34 UTC 
OK - SI20

Using a 3.0 DC and 3.0 cluster, it's possible to update the cluster to 3.1 when VM's are running.