Bug 1381168

Summary:	ovirt-engine 4.1 only supports 4.1 compatibility level which is not yet working
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	BLL.Storage	Assignee:	Allon Mureinik <amureini>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.1.0	CC:	bugs
Target Milestone:	ovirt-4.1.0-alpha	Keywords:	TestBlocker
Target Release:	---	Flags:	rule-engine: ovirt-4.1+ rule-engine: blocker+ rule-engine: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-15 14:55:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sandro Bonazzola 2016-10-03 10:08:49 UTC

- Installed ovirt-engine 4.1 from master
- Default datacenter compatibility is set to 4.1 and can't be changed.
- Deployed one host
- tried to add a data domain: vdsm fails with:"Domain version `4` is unsupported by this version of VDSM"


ovirt-engine-4.1.0-0.0.master.20161002221922.gitee66cd1.fc24.noarch
vdsm-4.18.999-662.git1c387c5.fc24.x86_64

In general, I would expect ovirt-engine 4.1 to allow compatibility level down to 4.0 as a minimum.

Comment 3 Allon Mureinik 2016-11-29 19:28:10 UTC

This was fixed on master a long time ago. Moving to MODIFIED to be verified formally when we have a build.

Comment 4 Sandro Bonazzola 2016-12-12 13:57:38 UTC

The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 5 Raz Tamir 2016-12-13 17:49:36 UTC

Verified on 4.1.0-0.2.master.20161212071212.git8a015dd.el7.centos