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 1514008

Summary: In the plan configuration dialog, the user can enter too large node counters
Product: Red Hat OpenStack Reporter: Udi <ukalifon>
Component: openstack-tripleo-uiAssignee: Jason E. Rist <jrist>
Status: CLOSED WONTFIX QA Contact: Arik Chernetsky <achernet>
Severity: low Docs Contact:
Priority: low    
Version: 12.0 (Pike)CC: belwell, jjoyce, jschluet, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-15 05:16:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Udi 2017-11-16 13:33:34 UTC
Description of problem:
In the deployment page, the increment and decrement buttons for the role counters are disabled when they can't be changed further (when there are no more nodes available that are tagged to this role). However this verification is missing when editing the plan parameters in the plan configuration dialog, and the user can choose any number.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.4.3-2.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. In the deployment page, note how many nodes are available for every role.
2. Open the plan configuration dialog, and in the parameters tab enter a higher number in the various role counters.
3. Save the changes.


Actual results:
The counter in the deployment page is set to an illegal value, and shows up in red.


Expected results:
Validations in the deployment configuration dialog should prevent illegal values from being entered.

Comment 3 Jason E. Rist 2018-08-15 05:16:59 UTC
Sufficient that this shows up red.  Low enough priority that we won't be fixing.