Bug 1853274
| Summary: | No response when creating operator instance using “Configure via: Form View” | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> | ||||
| Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | aos-bugs, jokerman, spadgett, wduan, xiaocwan, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: Catch logic for failed operand form submit was attempting to access a deep property in the resulting error object that is not always defined.
Consequence: For specific failed request types, this would cause a runtime error.
Fix: Update the catch logic for operand form submit failures to always use `error.message`, and fallback to
Result:
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-30 18:56:59 UTC | Type: | --- | ||||
| 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: | 1846863 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Comment 1
Scott Dodson
2020-07-02 12:29:01 UTC
Created attachment 1702160 [details]
Verification screenshot
This instance could be created successfully (attached the screen recording for refer) Verified on 4.5.0-0.nightly-2020-07-23-023500 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:3028 |