Bug 1224612

Summary:	[New] - Additional features supported in cluster should be always checked by default.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	rhsc	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	asrivast, nlevinki, rhs-bugs, sabose, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhsc-3.1.0-58	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 05:29:27 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:	1202842

Description RamaKasturi 2015-05-25 06:42:04 UTC

Description of problem:
When trying to create a new cluster from the console by default all the additional features supported in the cluster should be checked by default. As of now user has to explicitly go and select them.

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.0.scratch.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Try creating a new cluster.
2. 
3.

Actual results:
By default all the additional features supported in the cluster are not checked by default.

Expected results:
By default all the additional features supported in the cluster should be checked by default.

Additional info:

Comment 2 RamaKasturi 2015-06-03 09:41:41 UTC

Verified and works fine with build rhsc-3.1.0-0.58.master.el6.noarch.

Now i do not see any option called "Additional feature support" while creating new cluster. It is hidden by default and when user tries to create a 3.5 cluster from console it will have all the features enabled by default.

Comment 4 errata-xmlrpc 2015-07-29 05:29:27 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://rhn.redhat.com/errata/RHEA-2015-1494.html