Bug 1173815 - [RHEVM-RHS] Unable to add RHS 3.0 Update3 Nodes to cluster with 3.5 compatibility in RHEVM 3.5
Summary: [RHEVM-RHS] Unable to add RHS 3.0 Update3 Nodes to cluster with 3.5 compatibi...
Keywords:
Status: CLOSED DUPLICATE of bug 1181032
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.5.0
Hardware: x86_64
OS: All
unspecified
high
Target Milestone: ---
: 3.6.0
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard: gluster
Depends On:
Blocks: 890517
TreeView+ depends on / blocked
 
Reported: 2014-12-13 08:44 UTC by SATHEESARAN
Modified: 2016-02-10 18:58 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-02 07:52:55 UTC
oVirt Team: Gluster
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2014-12-13 08:44:53 UTC
Description of problem:
-----------------------
Unable to add RHSS 3.0 Update3 Nodes to RHEVM 3.5


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHEVM 3.5 vt13.1

How reproducible:
------------------
Consistent

Steps to Reproduce:
-------------------
1. Create a DC of compatibility 3.5
2. Create a gluster enabled cluster ( of compatibility 3.5 )
3. Add RHSS 3.0 Update3 Nodes to the cluster.

Actual results:
---------------
Unable to add RHSS 3.0 Update3 nodes to the cluster

Actual error as seen on RHEVM UI - "Host RHSS1 is compatible with versions (3.0,3.1,3.2,3.3,3.4) and cannot join Cluster gluster-cluster which is set to version 3.5"

Expected results:
-----------------
RHSS 3.0 Update3 should get added to 3.5 compatible gluster cluster.

Comment 1 SATHEESARAN 2014-12-13 08:46:57 UTC
RHSS 3.0 Update3 has VDSM version of 4.14*
But I believe RHEVM 3.5 operates with VDSM 4.15*
Hope this is the problem

VDSM as available in RHSS 3.0 Update3 :

[root@dhcp37-200 ~]# rpm -qa | grep -i vdsm
vdsm-gluster-4.14.7.3-1.el6rhs.noarch                                                                                                                                   
vdsm-cli-4.14.7.3-1.el6rhs.noarch                                                                                                                                       
vdsm-python-zombiereaper-4.14.7.3-1.el6rhs.noarch                                                                                                                       
vdsm-python-4.14.7.3-1.el6rhs.x86_64                                                                                                                                    
vdsm-4.14.7.3-1.el6rhs.x86_64                                                                                                                                           
vdsm-xmlrpc-4.14.7.3-1.el6rhs.noarch                                                                                                                                    
vdsm-reg-4.14.7.3-1.el6rhs.noarch

Comment 2 SATHEESARAN 2014-12-13 08:51:32 UTC
Bala,

Can the VDSM in RHSS 3.0 Update3 (VDSM 4.14*) could be updated to VDSM 4.15* ?
In that case, this bug could be moved to RHS product & VDSM component.

Comment 3 Dan Kenigsberg 2014-12-15 13:38:10 UTC
Why is this a bug? clusterLevel 3.5 was introduced in vdsm-4.16.z. Older Vdsms (such as 4.14) should NOT be allowed into a 3.5 cluster.

Comment 4 Sahina Bose 2014-12-22 05:26:17 UTC
Dan,
I think the bug is about RHSS node not supporting the latest vdsm 4.16.x 
RHSS 3.0 nodes are packaged with vdsm 4.14.x and hence are not supported in 3.5 cluster levels.
The question was whether to upgrade the vdsm version in RHSS 3.0 update release. For now, it was decided not to.

Comment 5 Scott Herold 2015-01-02 15:18:13 UTC
It seems that this is not a RHEV bug, as RHEV is oeprating as expected per Comment 3.  Please move bug to RHSS for proper follow-up action to update vdsm compatibility.  Based on delivery in RHSS, I will need to push BZ 890517 to RHEV 3.6.

Comment 6 Bala.FA 2015-02-02 07:52:55 UTC

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

Comment 7 SATHEESARAN 2015-02-02 08:01:38 UTC
This bug is closed as per comment5 and removing needinfo


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