Bug 975055

Summary:	[RHSC] Cluster Compatibility Version version should default to the latest version
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Matt Mahoney <mmahoney>
Component:	rhsc	Assignee:	Kanagaraj <kmayilsa>
Status:	CLOSED ERRATA	QA Contact:	Matt Mahoney <mmahoney>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	dpati, dtsang, kmayilsa, knarra, mmahoney, pprakash, rhs-bugs, sabose, sankarshan, sdharane, sharne, ssampat
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	CB11	Doc Type:	Bug Fix
Doc Text:	Previously, while creating a new cluster, the lower 'Cluster Compatibility Version' was selected in the 'New Cluster' dialog box. Now, with this update, the highest compatibility version is selected by default.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-25 07:31:17 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:

Description Matt Mahoney 2013-06-17 14:11:07 UTC

Description of problem:
When creating a new cluster, the default Comparability Version should be the latest and not the first version.

Currently, when creating a cluster (Big Bend release) the comparability version defaults to 3.1, and not 3.2, but should default to 3.2.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Dusmant 2013-10-10 11:23:27 UTC

This would be taken up in RHSC future release

Comment 4 Matt Mahoney 2013-12-13 21:10:56 UTC

Verified in cb11.

Comment 5 Shalaka 2014-01-07 06:31:33 UTC

Please review the edited DocText and signoff.

Comment 6 Kanagaraj 2014-01-16 07:00:07 UTC

doc_text looks good.

Comment 8 errata-xmlrpc 2014-02-25 07:31:17 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html