Bug 1109912 - RHEV 3.3.2 doesn't work with vdsm-4.14.7-3.el6ev
Summary: RHEV 3.3.2 doesn't work with vdsm-4.14.7-3.el6ev
Keywords:
Status: CLOSED DUPLICATE of bug 1098767
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-16 15:35 UTC by Petr Spacek
Modified: 2014-06-19 05:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-19 05:46:48 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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