Bug 868993 - engine: we can create/attach a floating disk when we are still in 3.0 DC and Cluster
Summary: engine: we can create/attach a floating disk when we are still in 3.0 DC and ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.1.0
Assignee: Tal Nisan
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-22 17:02 UTC by Dafna Ron
Modified: 2016-02-10 20:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-22 20:24:28 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (185.29 KB, application/x-gzip)
2012-10-22 17:02 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-10-22 17:02:24 UTC
Created attachment 631639 [details]
logs

Description of problem:

I upgraded my 3.0 setup to 3.1 but did not update the hosts/Cluster or DC to 3.1 and I was able to create a floating disk and attach it to a vm. 

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

3.0 -> si21.1

How reproducible:

100%

Steps to Reproduce:
1. upgrade a 3.0 setup to si21.1
2. leave hosts/DC/Cluster with 3.0 level. 
3. create a floating disk -> attach to vm
  
Actual results:

we can create and attach a floating disk with compatibility of 3.0

Expected results:

this feature is supported for 3.1 only so we should allow this until all DC is updated to 3.1

Additional info: logs

Comment 1 Ayal Baron 2012-10-22 20:24:28 UTC
I actually see no reason to block this in 3.0 (vdsm doesn't care so host compatibility is not an issue).
Checked the code as well and I couldn't find any issue.


Note You need to log in before you can comment on or make changes to this bug.