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

Bug 1109912

Summary:	RHEV 3.3.2 doesn't work with vdsm-4.14.7-3.el6ev
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Petr Spacek <pspacek>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, gklein, iheim, lpeer, oourfali, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-19 05:46:48 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:

Description Petr Spacek 2014-06-16 15:35:25 UTC

Description of problem:
I did upgrade on RHEL 6 hypervisor and then host activation failed with message:
"Host belka is installed with VDSM version (4.14) and cannot join cluster IDM_BRQ which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]."

Version-Release number of selected component (if applicable):
rhevm-3.3.2-0.50.el6ev.noarch
vdsm-4.14.7-3.el6ev.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. Install RHEV rhevm-3.2.6-0.50.el6ev.noarch
2. Install hypervisor with VDSM < vdsm-4.14.7-3.el6ev.x86_64. Now RHEV and hypervisor work together.
3. Upgrade VDSM to vdsm-4.14.7-3.el6ev.x86_64 and try to activate the host.

Actual results:
Error "Host belka is installed with VDSM version (4.14) and cannot join cluster IDM_BRQ which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]."

Expected results:
Ordinary 'yum upgrade' on RHEL 6.z hypervisor should not break existing environment. Even the erratum text (with VDSM) doesn't mention it.

Additional info:
Upgrade to rhevm-3.3.3-0.52.el6ev.noarch allowed me to activate the hypervisor.

Comment 1 Oved Ourfali 2014-06-19 05:46:48 UTC

This issue was reported in Bug 1098767, and was fixed in 3.3.3.

*** This bug has been marked as a duplicate of bug 1098767 ***