Bug 1905941 - Page goes to error after create catalogsource
Summary: Page goes to error after create catalogsource
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-09 11:07 UTC by Yanping Zhang
Modified: 2021-02-24 15:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Catalog source Status field is mandatory, even if not in place everytime. Consequence: Create catalogsource from console on page, results into a runtime TypeError Fix: Add optional chaining to catalog source Status field Result: Create catalogsource from console on page wont result into a runtime TypeError
Clone Of:
Environment:
Last Closed: 2021-02-24 15:41:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
type-error (137.39 KB, image/png)
2020-12-09 11:07 UTC, Yanping Zhang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7494 0 None closed Bug 1905941: Add optional chaining to catalog source Status field 2021-01-15 13:25:20 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:41:35 UTC

Description Yanping Zhang 2020-12-09 11:07:05 UTC 
Created attachment 1737875 [details]
type-error

Description of problem:
Create catalogsource from console on page: cluster setting->global configuration->operatorhub->source->"Create CatalogSource" 
After click create, the page goes to error: "Oh no! Something went wrong." 

Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2020-12-08-141245

How reproducible:
Always

Steps to Reproduce:
1. Go to catalogsource create page: cluster setting->global configuration->operatorhub->source->"Create CatalogSource"
2.After set required fields, click "Create".
3.

Actual results:
2.The page goes to error: "Oh no! Something went wrong." 
There is TypeError in detail info(the error is not the same every time):" Cannot read property 'connectionState' of undefined"

Expected results:
2. Should show page normally.

Additional info:
Comment 4 Yanping Zhang 2020-12-21 06:45:29 UTC 
Checked on ocp 4.7 cluster with payload 4.7.0-0.nightly-2020-12-20-031835, now could create catalogsource successfully without error from page: cluster setting->global configuration->operatorhub->source->"Create CatalogSource"
The bug is fixed.
Comment 6 errata-xmlrpc 2021-02-24 15:41:14 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.7.0 security, bug fix, and enhancement 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-2020:5633
Note You need to log in before you can comment on or make changes to this bug.