Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1234320

Summary:	Vdsm for EL7 should not allow engine version lower than 3.5
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	vdsm	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	bazulay, danken, ecohen, gklein, lpeer, lsurette, lsvaty, oourfali, pstehlik, sherold, s.kieske, ycui, yeylon, ylavi
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.5.4
Hardware:	x86_64
OS:	Linux
Whiteboard:	infra
Fixed In Version:		Doc Type:	Release Note
Doc Text:	This release defers the ability to use VDSM in cluster versions 3.0 to 3.3. Over el6, vdsm-3.5 supports all clusters and Managers from 3.0 to 3.5. Over el7 and Fedora, VDSM stops supporting clusters below 3.4 and Managers below 3.3. Support for 3.4 Managers stays as tech-preview over el7.	Story Points:	---
Clone Of:	1229177	Environment:
Last Closed:	2015-09-03 18:12:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1229177
Bug Blocks:

Comment 1 Sven Kieske 2015-06-24 11:48:18 UTC

Hi,

Please also write some documentation how such upgrades should be handled (upgrade first engine, then vdsm? the other way around? all hosts in a cluster at once? move upgraded hosts to another cluster?) what's the current best pratice
for whole datacenter upgrades with minimal downtime for different storage scenarios?

Comment 3 Lukas Svaty 2015-07-22 10:58:49 UTC

verified in vt16.3
supported 3.4, 3.5
not supported < 3.4

Comment 5 errata-xmlrpc 2015-09-03 18:12:59 UTC

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/RHBA-2015-1729.html