Bug 1167572

Summary: Compatibility Version changes to highest value while editing Cluster
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Ramesh N <rnachimu>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: Sachin <sashinde>
Severity: medium Docs Contact:
Priority: low    
Version: rhgs-3.0CC: asriram, divya, kchidamb, mzywusko, nlevinki, rcyriac, rhinduja, rhs-bugs, rhsc-qe-bugs, rnachimu, sabose, sankarshan, sashinde, shtripat, ssampat
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhsc-3.1.3-0.71 Doc Type: Bug Fix
Doc Text:
Previously, when the cluster version was edited in the "Edit Cluster" dialog box in the Red Hat Storage Console, the compatible version field got loaded with the highest available compatibility version and the current version of the cluster was not displayed. With this fix, the cluster version is displayed correctly.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 05:27:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1153907, 1299184    
Attachments:
Description Flags
Edit Cluster screen shot none

Description Ramesh N 2014-11-25 05:35:13 UTC 
Created attachment 961006 [details]
Edit Cluster screen shot

Description of problem:

Compatibility Version changes to highest value while editing Cluster.

Version-Release number of selected component (if applicable):

RHSc 3.0.0

How reproducible:

Always

Steps to Reproduce:
1. Create a cluster with Compatibility Version 3.2
2. Edit the cluster
3. Compatibility Version changes automatically to 3.4
Actual results:

 Compatibility Version changes to 3.4 (Highest possible as of RHSC 3.0.0)

Expected results:

  Compatibility version should not change automatically.
Comment 2 Ramesh N 2014-11-25 05:59:18 UTC 
Note: This will not impact the customers who are already in the highest compatibility version(3.4).
Comment 3 Pavithra 2014-11-25 07:21:34 UTC 
Hi Shubhendu, 

I see this bug added as a known issue in the known issue tracker bug (1153907) for the 3.0.3 release. Can you please add the doc text for this known issue?
Comment 4 Pavithra 2014-12-08 09:27:46 UTC 
Hi Karnan,

Please review the edited doc text for technical accuracy in the doc text field and sign off.
Comment 5 Karnan 2014-12-08 10:31:17 UTC 
Hi Pavithra,

The doc text looks good.
Comment 7 Sahina Bose 2015-12-24 11:37:00 UTC 
This bug has been fixed as part of fix for Bug 1290748

Triveni, can u confirm?
Comment 9 Triveni Rao 2016-03-28 08:36:27 UTC 
This bug is verified and found no issues with the fixed in version :rhsc-3.1.3-0.71

Steps tested:
1. Create a cluster with cluster version 3.2
2. Edit the cluster.
3. Check the version

As expected cluster version did not change.
Comment 11 Divya 2016-06-08 08:01:49 UTC 
Sahina,

Could you review and sign-off the edited doc text.
Comment 12 Sahina Bose 2016-06-08 08:41:43 UTC 
acked
Comment 14 errata-xmlrpc 2016-06-23 05:27:01 UTC 
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://access.redhat.com/errata/RHBA-2016:1242