Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1366748 - [RFE] [API] API deployments allow setting openshift_storage_size to invalid value
Summary: [RFE] [API] API deployments allow setting openshift_storage_size to invalid v...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-server
Version: 1.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-12 17:05 UTC by Landon LaSmith
Modified: 2018-01-29 20:23 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1356682 None None None Never

Internal Links: 1356682

Description Landon LaSmith 2016-08-12 17:05:00 UTC
Enhancement: Deploying QCI via the fusor api will allow setting openshift_storage_size to zero while a zero value will return an error during deployment validation.

Steps to Reproduce:
1. Create a RHEV deployment using the fusor API
2. Specify a value for openshift_storage size that won't validate 
PUT /fusor/api/v21/deployments/<deployment id -d

  {'deployment': {
       'openshift_storage_size': 0}


This API call should return error when trying to set openshift_storage_size to a value < minimum recommended size.

Comment 1 John Matthews 2016-08-12 17:50:51 UTC
We punted this from GA because our current workflow allows building up a deployment over several invocations....i.e. we expect incomplete/partial data as the deployment object is built up.

Post GA we can re-examine the API to decide if there is a better alternative.


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