Bug 1003656

Summary: Cannot add RHS 2.1 to 'Gluster Service Enabled' Cluster of Compatibility version 3.3 on RHEVM 3.3
Product: Red Hat Enterprise Virtualization Manager Reporter: Rejy M Cyriac <rcyriac>
Component: ovirt-engine-webadmin-portalAssignee: Sahina Bose <sabose>
Status: CLOSED NEXTRELEASE QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, ecohen, iheim, ngupta, Rhev-m-bugs, sabose, scohen, yeylon
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-13 07:30:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
boot-strap logs from RHS 2.1 server none

Description Rejy M Cyriac 2013-09-02 14:55:53 UTC
Created attachment 792890 [details]
boot-strap logs from RHS 2.1 server

Description of problem:
Created Data Center and 'Gluster Service Enabled' Cluster of compatibility version 3.3. On adding RHS 2.1 server to the cluster, the entire boot-strapping process proceeds, and the host is set to 'Up' state. Immediately after that, the host is moved to 'Non-Operational' state with the following message in the log.

Host <RHShost> is compatible with versions (2.0,3.0,3.1,3.2) and cannot join Cluster <ClusterName> which is set to version 3.3.

Version-Release number of selected component (if applicable):
RHEVM 3.3 IS 12 (3.3.0-0.18.master.el6ev)

How reproducible:


Steps to Reproduce:
1.Create Data Center and 'Gluster Service Enabled' Cluster with compatibility version 3.3
2.Try to add RHS 2.1 server to cluster
3.

Actual results:
The RHS 2.1 server is moved to 'Non-Operational' state with the following message in the log.

Host <RHShost> is compatible with versions (2.0,3.0,3.1,3.2) and cannot join Cluster <ClusterName> which is set to version 3.3.

Expected results:
The RHS 2.1 server must be added successfully to the cluster

Additional info:

Comment 1 Rejy M Cyriac 2013-09-02 15:05:43 UTC
No issues in adding the RHS 2.1 server, if the compatibility version is 3.2

Comment 2 Itamar Heim 2013-09-02 20:26:43 UTC
sahina - iirc, this is a known limitation until RHS will rebase to a 3.3 compatible vdsm version?

Comment 3 Sahina Bose 2013-09-03 03:13:25 UTC
Yes, the RHS 2.1 reports vdsm cluster compatibility level 3.2

The Corbett release of RHS will support 3.3 cluster level as well

Comment 5 Itamar Heim 2013-09-13 07:30:43 UTC
closing next release as it will be fixed with the next release