Bug 928926 - [rhsc-cli] should not be able to create a cluster with both gluster_service and virt_service enabled
Summary: [rhsc-cli] should not be able to create a cluster with both gluster_service a...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc-cli
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: Mike McCune
URL:
Whiteboard:
Depends On:
Blocks: 957769 1035040
TreeView+ depends on / blocked
 
Reported: 2013-03-28 18:19 UTC by Dustin Tsang
Modified: 2015-08-26 10:19 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-08-26 10:19:33 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.