Red Hat Bugzilla – Bug 979151
[RHSC] Adding a RHS 2.0+ node to a 3.2 cluster fails with no indication to the user as to why
Last modified: 2016-04-18 06:06:26 EDT
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):
Steps to Reproduce:
1. Create 3.2 cluster
2. Added two RHS 2.1 nodes to cluster
3. Add RHS 2.0+ node
The RHS2.0+ node should be prevented from being added to a 3.2 cluster with RHS2.1 nodes.
Note: the same RHS2.0+ nodes add successfully into a 3.1 cluster, as would be expected.
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.
Created attachment 766410 [details]
Screenshot of 3.1 host
Matt, please let us know if you see details similar to one in attachment.
Retested. Validated that adding a RHS2.0+ host to a 3.2 Cluster is resulting in a compatibility error message as expected. Closing bug.