Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1796083

Summary: Create Receiver page loads forever when Prometheus API request returns an error
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: David Taylor <dtaylor>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Prometheus API request returns an error. Consequence: 'Create Receiver' for Alertmanager (Admin-> ClusterSettings -> AlertManager) loads indefinitely. Fix: Added try/catch Result: 'Create Receiver' will display an appropriate error message instead of loading indefinitely.
Story Points: ---
Clone Of: Environment:
Version: 4.4.0-0.ci-2020-01-28-150858 Cluster ID: b91b6151-f75a-4bdd-901b-aad4537e7d2e Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Last Closed: 2020-05-04 11:27:29 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
Page stuck in loading state on error
none
Error message when prometheus API requests error none

Description Samuel Padgett 2020-01-29 14:59:15 UTC
Created attachment 1656309 [details]
Page stuck in loading state on error

If the Prometheus API returns an error, the Create Receiver page never loads. We should handle the error and show the user an error message. See screenshot.

Comment 2 Yadan Pei 2020-02-05 02:44:03 UTC
Created attachment 1657727 [details]
Error message when prometheus API requests error

Now kubeadmin user opens Create Receiver page will see an error message instead of loading forever. verified on 4.4.0-0.nightly-2020-02-04-171905

Comment 4 errata-xmlrpc 2020-05-04 11:27:29 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:0581