Bug 1044511

Summary:	[RHS-C] Remove Cluster Compatibility Version 3.1 as we don't support management of RHS 2.0.z nodes
Product:	Red Hat Gluster Storage	Reporter:	Prasanth <pprakash>
Component:	rhsc	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.1	CC:	dtsang, knarra, mmahoney, pprakash, rhs-bugs, rnachimu, sabose, sdharane, sharne, ssampat
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cb13	Doc Type:	Bug Fix
Doc Text:	Previously, the Cluster Compatibility Version '3.1', which is not supported was displayed in the Red Hat Storage Console UI. Now, only the supported Cluster Compatibility Versions are displayed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-25 08:09:26 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:

Description Prasanth 2013-12-18 13:23:10 UTC

Description of problem:

We need to remove Cluster Compatibility Version 3.1 from UI as RHSC Corbett management of RHS 2.0.z nodes is NOT supported.


Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.2-0.27.beta.el6_5


How reproducible: Always


Steps to Reproduce:
1. Click on Clusters and select New
2. Expand the drop down of "Compatibility Version"
3.

Actual results: Compatibility Versions 3.1, 3.2 and 3.3 are listed


Expected results: Since RHSC management of RHS 2.0.z nodes is NOT supported, is there a need for keeping the 3.1 Compatibility Version in the UI?


Additional info:

Comment 2 Matt Mahoney 2013-12-20 19:47:34 UTC

Verified in cb13.

Comment 3 Shalaka 2014-01-27 10:50:05 UTC

Please review the edited Doc Text and signoff.

Comment 4 Ramesh N 2014-01-28 06:03:49 UTC

Doc text looks good

Comment 6 errata-xmlrpc 2014-02-25 08:09:26 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