Bug 1839017 - Status errors, if present, are not shown on submit of edit application forms
Summary: Status errors, if present, are not shown on submit of edit application forms
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: divgupta
QA Contact: Gajanan More
Depends On:
Blocks: 1840588
TreeView+ depends on / blocked
Reported: 2020-05-22 10:38 UTC by divgupta
Modified: 2020-07-13 17:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1840588 (view as bug list)
Last Closed: 2020-07-13 17:41:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 5534 0 None closed Bug 1839017: Show status errors on form save 2020-07-02 15:08:20 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:41:27 UTC

Description divgupta 2020-05-22 10:38:32 UTC
Description of problem:
When editing app resources using the edit application forms, errors occurred after creating the update request are not shown in the forms.

How reproducible: Always

Steps to reproduce:
1.Create an application using the add flows
2.From created application node's context menu select Edit <app-name> item to open edit form
3.Edit property of any resource that will throw error after creating update request
4.Notice error is not shown in the form footer

Actual Results:
Error is not shown

Expected Results:
Error should be shown

Comment 4 Gajanan More 2020-05-27 10:30:09 UTC
I have validated the bugzilla on:
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 5 errata-xmlrpc 2020-07-13 17:41:07 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.