#7215 HTTP 503 on staging OpenShift
Closed: Fixed 2 years ago Opened 2 years ago by bowlofeggs.

  • Describe what you need us to do:
    When I visit staging OpenShift, I receive an HTTP 503 code. The CLI also has troubles:
$ oc get pods
Error from server (InternalError): an error on the server ("<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>500 Proxy Error</title>\n</head><body>\n<h1>Proxy Error</h1>\nThe proxy server could not handle the request <em><a href=\"/api/v1/namespaces/bodhi/pods\">GET&nbsp;/api/v1/namespaces/bodhi/pods</a></em>.<p>\nReason: <strong>Error during SSL Handshake with remote server</strong></p><p />\n<hr>\n<address>Apache/2.4.34 (Fedora) Server at os.stg.fedoraproject.org Port 443</address>\n</body></html>") has prevented the request from succeeding (get pods)
  • When do you need this? (YYYY/MM/DD)
    As soon as convenient.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    If we stop using Bodhi or OpenShift.

  • If we cannot complete your request, what is the impact?
    I cannot see the Bodhi web server's logs to aid in my testing of the 3.10.0 beta.


This happened because somehow the router pods got deployed to masters and took over port 443, so the api wasn't running on them. The current generation of router pods doesn't have the node selector, so it runs on anything, the next gen one has the correct node selector so it will only run on os-node01/os-node02, but it's failing to deploy due to some stats/logging I was trying to enable not working.

Will get that fixed today hopefully.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata