+++ This bug was initially created as a clone of Bug #1106459 +++ 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: --- Additional comment from RamaKasturi on 2014-06-09 08:08:56 EDT --- Attaching the engine logs http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1106459/ --- Additional comment from RHEL Product and Program Management on 2014-06-09 08:11:57 EDT --- This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. --- Additional comment from Dusmant on 2014-06-11 00:44:55 EDT --- 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 ) --- Additional comment from Dusmant on 2014-06-11 00:46:36 EDT --- 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. --- Additional comment from RHEL Product and Program Management on 2014-06-11 00:52:10 EDT --- This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. --- Additional comment from RamaKasturi on 2014-06-11 02:25:52 EDT --- 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. --- Additional comment from Shalaka on 2014-06-24 13:45:08 EDT --- Please review edited doc text and sign off. --- Additional comment from Shubhendu Tripathi on 2014-06-25 00:26:43 EDT --- 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." --- Additional comment from RHEL Product and Program Management on 2014-06-27 19:03:49 EDT --- This request has been proposed as a blocker, but a release flag has not been requested. Please set a release flag to ? to ensure we may track this bug against the appropriate upcoming release, and reset the blocker flag to ?. --- Additional comment from RHEL Product and Program Management on 2014-06-27 19:16:05 EDT --- Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. --- Additional comment from RHEL Product and Program Management on 2014-06-27 19:32:08 EDT --- This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
This issue was seen with RHEVM 3.4 and RHS 3.0[glusterfs-3.6.0.24-1.el6rhs]. 1. Create a gluster enabled cluster of 3.4 2. Add RHSS Nodes to the cluster 3. Create one more gluster enabled cluster of 3.4 4. Move the RHS Node from one gluster cluster to other, by moving the node to MAINTENANCE mode and editing it. Actual result: There was a error "Operation Cancelled: Error While executing action: Host CPU type is not supported in this cluster compatibility version or is not supported at all" This bug was already found with RHSC as https://bugzilla.redhat.com/show_bug.cgi?id=1106459 and so cloned as this bug for RHEVM product
(In reply to SATHEESARAN from comment #1) > This issue was seen with RHEVM 3.4 and RHS 3.0[glusterfs-3.6.0.24-1.el6rhs]. > > 1. Create a gluster enabled cluster of 3.4 > 2. Add RHSS Nodes to the cluster > 3. Create one more gluster enabled cluster of 3.4 > 4. Move the RHS Node from one gluster cluster to other, by moving the node > to MAINTENANCE mode and editing it. > > Actual result: There was a error "Operation Cancelled: Error While executing > action: Host CPU type is not supported in this cluster compatibility version > or is not supported at all" > > This bug was already found with RHSC as > https://bugzilla.redhat.com/show_bug.cgi?id=1106459 and so cloned as this > bug for RHEVM product As far as I saw the patch to address that is also merged. What are the action items required in this bug?
(In reply to Oved Ourfali from comment #2) > As far as I saw the patch to address that is also merged. > What are the action items required in this bug? With my initial discussion with Sahina, I got the feel like, this patch haven't made in to RHEV 3.4. If its merged already, could you please provide a patch URL, and move this bug ON_QA with suitable FIXED_IN_VERSION.
(In reply to SATHEESARAN from comment #3) > (In reply to Oved Ourfali from comment #2) > > As far as I saw the patch to address that is also merged. > > What are the action items required in this bug? > > With my initial discussion with Sahina, I got the feel like, this patch > haven't made in to RHEV 3.4. > > If its merged already, could you please provide a patch URL, and move this > bug ON_QA with suitable FIXED_IN_VERSION. One of your guys fixed that, and it will make it in to 3.5.0. Is that okay? If not, he should port it to 3.4.Z.
Closed for now. If the fix is needed anywhere please reopen and let me know what's blocking the porting to 3.4.Z.