Podman pull/push fails with 502 http code in QUAY

Solution Verified - Updated -

Environment

  • Red Hat Quay
    • 3.x

Issue

  • Podman pull fails with the following generic error:

    Error: parsing image configuration: Error fetching blob: invalid status code from registry 502 (Bad Gateway)

  • Podman push fails with the following generic error:

    Error: Error writing blob: Error initiating layer upload to /v2/repo/image/blobs/uploads/ in <registry>: received unexpected HTTP status: 502 Bad Gateway

Resolution

  1. As a primary solution, restart Quay instances to free up any locked-up workers, clean up temporary files, cache or get rid of any transient issues. Restart can help reset any problematic state.

    • For containerized Quay deployment:

      $ podman restart quay-container

    • For Quay operator deployment:

      $ oc delete pod quay-app

  2. 502 being a generic error, further search for specific Python traceback from Quay debug logs. Refer to individual KCSs given below. Diagnostic steps and Root Causes are covered there too.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments