Bug 1806615

Summary: Installed Operators: Runtime error viewing packageserver
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jokerman, yanpzhan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1806617 (view as bug list) Environment:
Version: 4.5.0-0.ci-2020-02-24-112808 Cluster ID: 92fc0c6b-bcdd-4c39-a547-e32e250de6d8 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Last Closed: 2020-07-13 17:20: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:
Bug Depends On:    
Bug Blocks: 1806617    
Attachments:
Description Flags
Error page none

Description Samuel Padgett 2020-02-24 15:56:53 UTC
Created attachment 1665472 [details]
Error page

Steps to reproduce:

1. Select all projects
2. Go to Operators -> Installed Operators
3. Select packageserver

You see a runtime error:

TypeError: "metadata.annotations is undefined"
    ClusterServiceVersionDetails clusterserviceversion.tsx:608
    React 17
    Redux 7
    watchK8sObject/</WS[id]</< k8s.ts:113
    watchK8sObject/</WS[id]< k8s.ts:113
    _invokeHandlers ws-factory.js:141
    _invokeHandlers ws-factory.js:139
    flushMessageBuffer

Comment 3 Yanping Zhang 2020-03-04 04:02:53 UTC
Checked on 4.5 cluster with payload 4.5.0-0.ci-2020-03-03-053944.
Steps to verify:
1. Select all projects
2. Go to Operators -> Installed Operators
3. Select packageserver, there is not runtime error now.
The bug is fixed, so move it to Verified.

Comment 6 errata-xmlrpc 2020-07-13 17:20: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, 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