Bug 2039756 - React missing key warning when open KnativeServing details
Summary: React missing key warning when open KnativeServing details
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.10.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 11:28 UTC by Christoph Jerolimov
Modified: 2022-03-10 16:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:38:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10823 0 None open Bug 2039756: Fix react warning on operator hub description component, used for example on the KnativeServing detail page 2022-01-12 11:31:48 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:39:00 UTC

Description Christoph Jerolimov 2022-01-12 11:28:02 UTC
Description of problem:
As a developer, I want an application without annoying react warnings. ;)

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

How reproducible:
Always

Steps to Reproduce:
1. Install OpenShift Serverless operator
2. Switch to knative-serving and create a KnativeServing resource from the operator detail page
3. Open the new resource (Knative Serving detail page)

Actual results:
React warning in the browser console

Expected results:
No warning

Additional info:
Local URL: http://localhost:9000/k8s/ns/knative-serving/clusterserviceversions/serverless-operator.v1.19.0/operator.knative.dev~v1alpha1~KnativeServing/knative-serving

Warning: Each child in a list should have a unique "key" prop.

Check the top-level render call using <div>. See https://reactjs.org/link/warning-keys for more information.
    at DescriptorConditions (http://localhost:9000/static/operand-893fa137265b571db0de.js:1505:3)
    at http://localhost:9000/static/operand-893fa137265b571db0de.js:3113:3
    at ConnectFunction (http://localhost:9000/static/vendors~main-8d9dae4cda3d40c5dc31.js:471471:75)
    at ErrorBoundary (http://localhost:9000/static/main-d8e9753ffc409a262095.js:44662:5)
    at Route (http://localhost:9000/static/vendors~main-8d9dae4cda3d40c5dc31.js:479302:29)
    at Switch (http://localhost:9000/static/vendors~main-8d9dae4cda3d40c5dc31.js:479508:29)

Comment 3 Christoph Jerolimov 2022-01-18 10:04:03 UTC
Don't see this warning anymore in local development. Mark this as verified because its not related to any user change.

Comment 6 errata-xmlrpc 2022-03-10 16:38:43 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056


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