Bug 1688613
| Summary: | Avoid duplicate error message for failed validation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> | ||||
| Component: | Dev Console | Assignee: | cvogt | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ruchir Garg <rgarg> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, nmukherj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: |
Feature:
When the introduction of the Developer console, some forms have been overhauled. Some fields, such as the name, now use client side validation to provide immediate feedback for invalid values.
Reason:
Error messages from the server are often long and unclear.
Result:
Client side validation will show an inline error message for invalid name values.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-01-23 11:03:45 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: | |||||||
| Attachments: |
|
||||||
|
Description
Yadan Pei
2019-03-14 05:42:15 UTC
Updating to dev console since the code has moved. It looks like this might have been fixed indirectly since it was opened. No longer reproducible as the forms have changed and include name validation that prevents the creation of the resource. Created attachment 1638956 [details]
name validation error
Verified on: https://openshift-release.svc.ci.openshift.org/releasestream/4.3.0-0.ci/release/4.3.0-0.ci-2019-11-22-122829 Firefox: 68.2.0esr As noted previously, the name now has validation client side. See attached screenshot. 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, 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-2020:0062 |