Bug 928926

Summary:	[rhsc-cli] should not be able to create a cluster with both gluster_service and virt_service enabled
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Dustin Tsang <dtsang>
Component:	rhsc-cli	Assignee:	Sahina Bose <sabose>
Status:	CLOSED WONTFIX	QA Contact:	Mike McCune <mmccune>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	asriram, dpati, kmayilsa, mmccune, rhs-bugs, sabose, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	When you create a cluster through API, it is currently possible to enable both gluster_service and virt_service, though this is not supported.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 10:19:33 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:	957769, 1035040

Description Dustin Tsang 2013-03-28 18:19:41 UTC

Description of problem:
The user should not be able to create a cluster with both gluster_serice and virt_service enabled. 

Version-Release number of selected component (if applicable):
add cluster --name aasdfsdfaslalala --cpu-id 'Intel SandyBridge Family' --gluster_service True --virt_service False --datacenter-name Default 

How reproducible:
100%

Steps to Reproduce:
1. run rhsc-shell
2. connect to the api
3. run the command "add cluster --name aasadsfdfsdfaslalala --cpu-id 'Intel SandyBridge Family' --gluster_service True --virt_service True --datacenter-name Default"

  
Actual results:
cluster was successfully created with both gluster_service and virt_service set to True.

Expected results:
Cluster should not be created. HTTP 40X should have been sent from the rhsc ovirt-engine with an error message.


Additional info:
also should not be able to create a cluster with both options off.

Comment 2 Pavithra 2013-09-03 08:41:08 UTC

Sahina,

Kindly review the doc text for the known issue and please sign off on the technical accuracy

Comment 3 Dusmant 2013-10-25 07:09:49 UTC

Out of Corbett

Comment 7 Dusmant 2015-08-26 10:19:33 UTC

We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant