Bug 1366748
| Summary: | [RFE] [API] API deployments allow setting openshift_storage_size to invalid value | ||
|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Landon LaSmith <llasmith> |
| Component: | fusor-server | Assignee: | John Matthews <jmatthew> |
| Status: | NEW --- | QA Contact: | Dave Johnson <dajohnso> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.0 | Keywords: | FutureFeature, Triaged |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
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. |
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.