Bug 916981

Summary: [RHEVM-RHS] Unable to add RHS2.0+ node to a "Gluster Cluster" inside a Data Center having Compatibility version set to 3.2
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: vdsmAssignee: Anjana Suparna Sriram <asriram>
Status: CLOSED NOTABUG QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: acathrow, dtsang, dyasny, ecohen, grajaiya, iheim, mmahoney, pprakash, Rhev-m-bugs, rhs-bugs, sabose, sdharane, shaines, shireesh, ssampat, tkatarki, vbellur, ykaul
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: gluster
Fixed In Version: Doc Type: Known Issue
Doc Text:
Since Anshi contains vdsm that supports functionality of cluster level 3.1, an Anshi node can only be added to a cluster having compatibility level of 3.1 in RHEV-M. In RHEV-M 3.2, when it releases, one will be able to create clusters with compatibility level of 3.0, 3.1 and 3.2. However user will not be able to add an Anshi node to a cluster with compatibility level set to 3.2. It can be added to a cluster with compatibility level set to 3.1 only.
 Story Points: ---
Clone Of: Environment:
virt rhev integration
Last Closed: 2013-05-13 06:46:25 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:
Attachments:
Description Flags
engine.log
none
vdsm.log none

Description Prasanth 2013-03-01 10:45:33 UTC 
Description of problem:

Unable to add RHS2.0+ nodes:

1. To a "Gluster Cluster" inside a Data Center having Compatibility version set to 3.2 and 

2. To a "Gluster Cluster" with Compatibility version set to 3.2 inside a Data Center having Compatibility version set to 3.1

Version-Release number of selected component (if applicable):

From RHEL6.4 engine:
rhevm-3.2.0-10.10.beta1.el6


From RHS2.0+ node:

ISO Used: RHS-2.0-20130219.3-RHS-x86_64-DVD1.iso

# cat /etc/issue
Red Hat Storage release 2.0 for On-Premise
Kernel \r on an \m

# rpm -qa |grep vdsm
vdsm-cli-4.9.6-19.el6rhs.noarch
vdsm-python-4.9.6-19.el6rhs.x86_64
vdsm-4.9.6-19.el6rhs.x86_64
vdsm-gluster-4.9.6-19.el6rhs.noarch
vdsm-reg-4.9.6-19.el6rhs.noarch

# rpm -qa |grep glusterfs
glusterfs-3.3.0.6rhs-2.el6rhs.x86_64
glusterfs-devel-3.3.0.6rhs-2.el6rhs.x86_64
glusterfs-fuse-3.3.0.6rhs-2.el6rhs.x86_64
org.apache.hadoop.fs.glusterfs-glusterfs-0.20.2_0.2-1.noarch
glusterfs-rdma-3.3.0.6rhs-2.el6rhs.x86_64
glusterfs-geo-replication-3.3.0.6rhs-2.el6rhs.x86_64
glusterfs-server-3.3.0.6rhs-2.el6rhs.x86_64
glusterfs-debuginfo-3.3.0.6rhs-2.el6rhs.x86_64


# rhn-channel -l
rhel-x86_64-server-6-rhs-2.0
rhel-x86_64-server-6.2.z
rhel-x86_64-server-sfs-6.2.z


How reproducible: Always


Steps to Reproduce:

Case A:

1. Create a Data Center with "Compatibility Version" set to 3.2
2. Create a "Enable Gluster Service" Cluster with "Compatibility Version" set to 3.2 (Here only 3.2 can be selected)
3. Add the latest RHS2.0+ ISO (RHS-2.0-20130219.3-RHS-x86_64-DVD1.iso) installed Host to the gluster cluster created above.
4. Watch the Events tab and engine logs.

Case B:

1. Create a Data Center with "Compatibility Version" set to 3.1
2. Create a "Enable Gluster Service" Cluster with "Compatibility Version" set to 3.2 (here, currently we are allowed to set the compatibility version to either 3.1 or 3.2, bug???)
3. Add the latest RHS2.0+ ISO (RHS-2.0-20130219.3-RHS-x86_64-DVD1.iso) installed Host to the gluster cluster created above.
4. Watch the Events tab and engine logs.
  
Actual results: Add Host fails with the following error in the "Events" tab in both the cases:

---
Host RHSHost is compatible with versions (3.0,3.1) and cannot join Cluster My32DC32GlusterCluster which is set to version 3.2.

Host RHSNode is compatible with versions (3.0,3.1) and cannot join Cluster My31DC32GlusterCluster which is set to version 3.2.
---


Expected results: Add Host should Pass, if we are allowing the user to add RHS2.0+ hosts to a 3.2 compatible cluster. If we don't allow RHS2.0+ hosts to a 3.2 cluster, please clarify on the same.


Additional info: engine logs and vdsm logs are attached.
Comment 1 Prasanth 2013-03-01 10:46:29 UTC 
Created attachment 704125 [details]
engine.log
Comment 2 Prasanth 2013-03-01 10:46:58 UTC 
Created attachment 704126 [details]
vdsm.log
Comment 3 Itamar Heim 2013-03-01 13:26:15 UTC 
error is perfectly clear - vdsm in the RHS node isn't compatible with a 3.2 cluster. you need a more advanced vdsm version to be in a 3.2 cluster (4.10, etc.).
Comment 5 Shireesh 2013-03-04 13:57:56 UTC 
There is no feature upgrade of RHS-C planned in RHS2.0+, and hence it will continue to have a vdsm that supports 3.1 only.
Comment 6 Gowrishankar Rajaiyan 2013-03-05 03:31:26 UTC 
This needs to be documented in our Quick Start Guide. Re-opening and re-assigning.
Comment 7 Shireesh 2013-03-05 06:46:55 UTC 
(In reply to comment #5)
> There is no feature upgrade of RHS-C planned in RHS2.0+, and hence it will
> continue to have a vdsm that supports 3.1 only.

Note that when I say it will support 3.1 only, I mean it can be added to a cluster with compatibility level set to 3.1. So it should work with RHEV-M 3.2 also, as long as the correct compatibility level is set on the cluster.
Comment 8 Sahina Bose 2013-05-13 06:46:25 UTC 
As per comments above, closing NOT A BUG