Description of problem: Editing a server when in maintenance i.e , moving the host to a different cluster results in the error "Error While executing action: Host CPU type is not supported in this cluster compatibility version or is not supported at all". Version-Release number of selected component (if applicable): rhsc-3.0.0-0.7.master.el6_5.noarch How reproducible: Always Steps to Reproduce: 1. Create a cluster of comaptibility version 3.4 2. Add a hos to the cluster. 3. Now move the host to maintenance. 4. click on the edit button. 5. change the cluster to default cluster. Actual results: It gives "Operation Cancelled: Error While executing action: Host CPU type is not supported in this cluster compatibility version or is not supported at all" Expected results: Host should be moved into default cluster. Additional info:
Attaching the engine logs http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1106459/
As discussed in the triage meeting : Kasturi will try the suggested workaround to see if that works or not. Most likely, this would NOT be a BLOCKER, if the workaround works. We should capture the work around in the doc-text. But we should fix this bug in upstream and keep it ready for 3.0.1 ( ASYNC Errata release )
For the time being, i am taking it out of Blocker? If the work-around does not work, then we should mark it as blocker.
The following scenarios does not work: 1) Moving a host to maintenance and editing the host to move it to a different cluster of same compatibility version does not work. 2) Moving a host to maintenance and editing the host to move it to a cluster of lesser compatibility version does not work. Tried the following workaround suggested by kanagaraj and it works. 1) Moved the host to maintenance, removed the host, created another cluster of same compatibility version and was able to add the host successfully to that cluster. 2) Moved the host to maintenance, removed the host, created another cluster of lesser compatibility version and was able to add the host successfully to that cluster.
Please review edited doc text and sign off.
It could be as below - "When host is in maintenance mode, moving host to a different cluster of same or lesser compatibility version, displays error. Workaround: Remove the host from the current cluster and add to another cluster."
From kanagaraj, i understand that these bugs have been moved to on_qa by errata. Since QE has not yet received the build i am moving this bug back to assigned state. Please move it on to on_qa once builds are attached to errata.
Verified and works fine with build rhsc-3.0.3-1.17.el6rhs.noarch. The following scenarios works: 1) Moving a host to maintenance and editing the host to move it to a different cluster of same compatibility version works. 2) Moving a host to maintenance and editing the host to move it to a cluster of lesser compatibility version works.
Hi Kanagaraj, Can you please review the edited doc text for technical accuracy and sign off?
looks good.
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-0039.html