Hide Forgot
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:
No issues in adding the RHS 2.1 server, if the compatibility version is 3.2
sahina - iirc, this is a known limitation until RHS will rebase to a 3.3 compatible vdsm version?
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
closing next release as it will be fixed with the next release