Description of problem: When newer versions of RHS nodes are released, there's an error in adding these nodes to already released version of RHSC For instance, we are unable to manage RHS 3.0 nodes using existing RHSC 2.1 U2 installations The error is "Host xxx is installed with VDSM version (4.14) and cannot join cluster yyy which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. " Version-Release number of selected component (if applicable): 2.1 Cause: RHSC VDC version was changed to 2.1 to reflect that RHS release name..and this has caused this feature to break. VDSM reports supportedENGINEs = ['3.0', '3.1', '3.2', '3.3', '3.4'] which does not match the VDC version = 2.1
Verified as fixed in rhsc-2.1.6-0.44.el6rhs.noarch. RHS 3 node can be added to RHSC 2.1 to both 3.3 and 3.2 compatible clusters. Marking as verified.
Hi Ramesh, Can you please review the edited doc text for technical accuracy and sign off?
Doc text looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0096.html