Bug 2020316 - https://console.redhat.com/openshift/overview refuses to load if too many clusters were installed
Summary: https://console.redhat.com/openshift/overview refuses to load if too many clu...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: General
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kathryn Dixon
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-04 15:18 UTC by Michal Vinkler
Modified: 2021-11-09 12:07 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 12:07:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Vinkler 2021-11-04 15:18:00 UTC
Description of problem:
https://console.redhat.com/openshift/overview refuses to load for my RH account 

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


How reproducible:
Always (using my RH account)

Steps to Reproduce:
1. Install and destroy several thousands of OCP clusters with your pull secret
2. Access https://console.redhat.com/openshift/overview 

Actual results:
This page is temporarily unavailable
Try refreshing the page. If the problem persists, contact your organization administrator or visit our status page for known outages.

Error details
Error code: undefined
Error: Network Error
Operation ID: N/A

Expected results:
The page loads

Additional info:
I work in Serverless QE and my pull secret is used in automated testing of Serverless operator (new OCP is installed, tests are run, OCP is destroyed).

I got to the point where several services refuse to work, including the status page not loading, or "ocm get /api/clusters_mgmt/v1/clusters" timing out.

Comment 1 Michal Vinkler 2021-11-09 12:07:05 UTC
I got an answer on Slack already, at the moment there is no solution for this issue. The only workaround is to create another corporate account.


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