Cant' upgrade to Quay 3.3.0: config not completed or is missing

Solution Verified - Updated -

Issue

When an upgrade to Quay 3.3.0 is initiated from a cluster running Quay 3.2.x or 3.1.x, the startup sequence of Quay 3.3.0 hangs and the registry is not loaded.

Environment

  • Quay 3.1.x
  • Quay 3.2.x
  • VM installation: RHEL 7/8
  • Kubernetes: OpenShift 3.11/4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In