Bug 2036044
| Summary: | Import flow: Resource limit form validation doesn't work reliable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Debsmita Santra <dsantra> | ||||
| Component: | Dev Console | Assignee: | Debsmita Santra <dsantra> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Mohammed Saud <msaud> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.9 | CC: | aos-bugs, nmukherj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.9.0 | ||||||
| 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: | 2022-01-10 08:50:47 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: | 2031082, 2036045 | ||||||
| Attachments: |
|
||||||
The JIRA bug was verified by Saud (https://issues.redhat.com/browse/ODC-6122) Verified on: Build: 4.9.0-0.nightly-2021-07-21-081948 Browser: Firefox 90 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.13 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0029 |
Created attachment 1848211 [details] invalid form validation Description of problem: When the user creates a Deployment with one of the Import from ... pages, she or he has the option to define a resource limit in the advanced option section. The resource limit section allows the user to define Request and Limit CPU cycles and Request and Limit memory. The form does not allow a limit value which is smaller then the request value. This form sometimes shows unexpected validations error if a unit is selected. It looks like that the unit is ignored when the number is changed. See attached video. Prerequisites (if any, like setup, operators/versions): None Steps to Reproduce 1. Switch to developer perspective 2. Add > Import from Git 3. Scroll down to Advanced options and click on Resource limits 4. Enter test data into the Resource limits forms 1. Broken case a) 1. 10 request CPU, keep millicores 2. 15 limit CPU, keep millicores 3. Switch limit to cores 4. Press Limit minus button until the value is below 10. 2. Broken case b) 1. 91 request CPU, keep millicores 2. 2 limit CPU, select cores 3. Press Limit plus button until value is 5 4. Press Resource plus button until value is 6 Actual results: It shows invalid form validation errors Expected results: It should not show form validation errors in that case Reproducibility (Always/Intermittent/Only Once): Always Build Details: 4.9 master (19c0a653cc420c4ecee6ca44bd1126b2ee06d6ed)