Bug 979151

Summary: [RHSC] Adding a RHS 2.0+ node to a 3.2 cluster fails with no indication to the user as to why
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Matt Mahoney <mmahoney>
Component: rhscAssignee: Kanagaraj <kmayilsa>
Status: CLOSED NOTABUG QA Contact: Sudhir D <sdharane>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: dtsang, kmayilsa, knarra, mmahoney, pprakash, rhs-bugs, sabose, sankarshan, ssampat
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: 2013-07-01 15:19: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:
Attachments:
Description Flags
Screenshot of 3.1 host none

Description Matt Mahoney 2013-06-27 18:42:52 UTC 
Description of problem:
Adding a RHS 2.0+ node into a 3.2 cluster with two RHS 2.1 nodes fails with no indication to the user as to the reason being due incomparability. The add just fails and goes into non-operational state, but the node should not have been allowed to be added from the start

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


How reproducible:


Steps to Reproduce:
1. Create 3.2 cluster
2. Added two RHS 2.1 nodes to cluster
3. Add RHS 2.0+ node

Actual results:


Expected results:
The RHS2.0+ node should be prevented from being added to a 3.2 cluster with RHS2.1 nodes.

Additional info:
Comment 1 Matt Mahoney 2013-06-27 18:45:03 UTC 
Note: the same RHS2.0+ nodes add successfully into a 3.1 cluster, as would be expected.
Comment 3 Kanagaraj 2013-06-28 05:50:08 UTC 
Following error message will be shown in the host-general tab
"Host's Compatibility Version doesn't match the Cluster's Compatibility Version."

Also there will be a event log "Host s3 is compatible with versions (2.0,3.0,3.1) and cannot join Cluster Default which is set to version 3.2."

Matt, please let me know if the above is not happening.
Comment 4 Sahina Bose 2013-06-28 05:53:03 UTC 
Created attachment 766410 [details]
Screenshot of 3.1 host
Comment 5 Sahina Bose 2013-07-01 13:47:35 UTC 
Matt, please let us know if you see details similar to one in attachment.
Comment 6 Matt Mahoney 2013-07-01 15:19:48 UTC 
Retested. Validated that adding a RHS2.0+ host to a 3.2 Cluster is resulting in a compatibility error message as expected. Closing bug.