Bug 2039743

Summary: React missing key warning when open operator hub detail page (and maybe others as well)
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Christoph Jerolimov <cjerolim>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: low    
Version: 4.10CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:38:43 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 Flags
fix-horizontal-nav-missing-key-warning.png none

Description Christoph Jerolimov 2022-01-12 10:45:53 UTC
Created attachment 1850340 [details]
fix-horizontal-nav-missing-key-warning.png

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. Open the browser console to see react warnings and errors
2. Navigate to the operator hub and install an operator, for example the Primer operator
3. Navigate to the installed operator detail page

Actual results:
You can see a react warning:
Warning: Each child in a list should have a unique "key" prop.
Check the render method of `HorizontalNav`.

Expected results:
No warning/error :)

Additional info:

Comment 3 Christoph Jerolimov 2022-01-20 14:09:14 UTC
This change only affects when running console the console in dev mode. On a local environment, I can not see any warning more on the operator detail page.

Tested the operator list and details page on 4.10.0-0.nightly-2022-01-20-082726 anyway, still works fine.

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