Bug 1521126 - [starter-us-west-1] Catalog is forever busy icon (seeing 429 response errors)
Summary: [starter-us-west-1] Catalog is forever busy icon (seeing 429 response errors)
Keywords:
Status: CLOSED DUPLICATE of bug 1521169
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Management Console
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-05 20:27 UTC by Steve Speicher
Modified: 2017-12-06 13:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 13:43:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Speicher 2017-12-05 20:27:51 UTC
Description of problem:

Looking at the Developer Console for Chrome web browser, I'm seeing 429s and initial login errors as well. Mostly, after one or 2 attempts, then I can login but the catalog never responds with content.

https://console.starter-us-west-1.openshift.com/console/

Some log response:

HTTP/1.1 429 Too Many Requests
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Content-Type, Content-Length, Accept-Encoding, X-CSRF-Token, Authorization, X-Requested-With, If-Modified-Since
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE, PATCH
Access-Control-Allow-Origin: https://console.starter-us-west-1.openshift.com
Access-Control-Expose-Headers: Date
Cache-Control: no-store
Content-Type: text/plain; charset=utf-8
Retry-After: 1
X-Content-Type-Options: nosniff
Date: Tue, 05 Dec 2017 20:21:24 GMT
Content-Length: 43


HTTP/1.1 403 Forbidden
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Content-Type
Access-Control-Allow-Methods: POST, GET, OPTIONS
Access-Control-Allow-Origin: https://console.starter-us-west-1.openshift.com
Cache-Control: no-cache
Content-Encoding: gzip
Content-Type: application/json; charset=utf-8
Date: Tue, 05 Dec 2017 20:21:25 GMT
Server: nginx
Set-Cookie: _mkra_ctxt=57cc4658bb5830d16623552e0699ae3f--403; path=/; max-age=5; HttpOnly; secure
Status: 403 Forbidden
Strict-Transport-Security: max-age=31557600; includeSubDomains; preload
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Intercom-Version: 729d1efde8fe56863ed00f67d013a4f51c5952ff
X-Request-Id: b051bhk9tc1mv4o6j750
X-Runtime: 0.046963
X-XSS-Protection: 1; mode=block
transfer-encoding: chunked
Connection: keep-alive

Comment 1 Jessica Forrester 2017-12-06 13:43:06 UTC
Yes its known this cluster is in a bad state currently

*** This bug has been marked as a duplicate of bug 1521169 ***


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