Bug 1834774 - React warning from traffic splitting dialog in topology
Summary: React warning from traffic splitting dialog in topology
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Christoph Jerolimov
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-12 11:54 UTC by Christoph Jerolimov
Modified: 2023-07-10 23:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:37:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5406 0 None closed Bug 1834774: Solve React warning when closing Traffic Splitting dialog 2020-06-24 02:21:15 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:38:13 UTC

Description Christoph Jerolimov 2020-05-12 11:54:53 UTC
Description of problem:
When open the Traffic Splitting modal dialog for a knative service and close it again there is an error in the browser console.


Version-Release number of selected component (if applicable):
4.5


How reproducible:
Always


Steps to Reproduce:
1. Install serverless operator
2. Create a namespace
3. Go to Dev console > Add > Container Image > Create knative service
4. In topology open the service details and press "Set Traffic Distribution"
5. Press on "Cancel"

Actual results:
"Warning: Can't perform a React state update...." is shown in the browser console.


Expected results:
No warning should be displayed.

Additional info:

Comment 3 Gajanan More 2020-05-19 06:00:46 UTC
I have validated the bugzilla on the
Build: 4.5.0-0.ci-2020-05-18-204038
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified

Comment 4 errata-xmlrpc 2020-07-13 17:37:59 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.

https://access.redhat.com/errata/RHBA-2020:2409

Comment 5 bottombend@gmail.com 2022-11-01 08:49:22 UTC Comment hidden (spam)
Comment 6 rouzman 2023-05-15 09:39:21 UTC Comment hidden (spam)

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