-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.4.0
-
False
-
False
-
Quay Enterprise
-
Undefined
-
Description of problem:
Meet 503 error when curl /health endpoint
Version-Release number of selected component (if applicable):
quay.io/quay/quay:3.4.0-1
How reproducible:
Always
Steps to Reproduce:
1.Deploy Quay via podman run
# podman run --restart=always -v `pwd`/quayv34/config:/conf/stack -v `pwd`/quayv34/storage:/storage -p 443:8443 -p 80:8080 --privileged=true -e QUAY_OVERRIDE_SERVICES="repomirrorworker=true" -e DEBUGLOG=true -d --name quay-v340-1 quay.io/quay/quay:3.4.0-1
2. curl http://quay-dyan.usersys.redhat.com/health
Actual results:
{"data":{"services":{"auth":true,"database":true,"disk_space":true,"jwtproxy":false,"registry_gunicorn":true,"service_key":true,"web_gunicorn":true}},"status_code":503}
Expected results:
Should not return error
Additional info:
the /status endpoint is normal
- curl http://quay-dyan.usersys.redhat.com/status
{"data":{"services":{"auth":true,"database":true,"redis":true,"storage":true}},"status_code":200}