Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1106459 - [RHSC] - Editing server when in Maintenance to move it to a different cluster, results in "Error While executing action: Host CPU type is not supported in this cluster compatibility version or is not supported at all".
[RHSC] - Editing server when in Maintenance to move it to a different cluster...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
3.0
Unspecified Unspecified
high Severity medium
: ---
: RHGS 3.0.3
Assigned To: Shubhendu Tripathi
RamaKasturi
: Regression, ZStream
Depends On:
Blocks: 1087818 1117131
  Show dependency tree / graph
 
Reported: 2014-06-09 08:04 EDT by RamaKasturi
Modified: 2015-05-15 13:38 EDT (History)
9 users (show)

See Also:
Fixed In Version: rhsc-3.0.2-1.16.el6rhs.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Previously, an error was displayed when moving a Red Hat Storage node from one Red Hat Storage Trusted Storage Pool to another. With this fix, checks that inhibits such movements are removed.
Story Points: ---
Clone Of:
: 1117131 (view as bug list)
Environment:
Last Closed: 2015-01-15 08:47:47 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 28575 master MERGED engine: skip cpu checks when moving host to gluster-cluster Never
Red Hat Product Errata RHBA-2015:0039 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update #3 2015-01-15 13:46:40 EST

  None (edit)
Description RamaKasturi 2014-06-09 08:04:27 EDT 
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:
Comment 1 RamaKasturi 2014-06-09 08:08:56 EDT 
Attaching the engine logs

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1106459/
Comment 3 Dusmant 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 )
Comment 4 Dusmant 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.
Comment 6 RamaKasturi 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.
Comment 7 Shalaka 2014-06-24 13:45:08 EDT 
Please review edited doc text and sign off.
Comment 8 Shubhendu Tripathi 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."
Comment 15 RamaKasturi 2014-10-17 01:40:55 EDT 
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.
Comment 16 RamaKasturi 2014-11-11 04:17:55 EST 
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.
Comment 18 Pavithra 2014-12-26 02:42:36 EST 
Hi Kanagaraj,

Can you please review the edited doc text for technical accuracy and sign off?
Comment 19 Kanagaraj 2014-12-26 03:08:36 EST 
looks good.
Comment 21 errata-xmlrpc 2015-01-15 08:47:47 EST 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.