Red Hat Quay registry upgrade stuck for RouteComponentDependencyError error in RHOCP 4

Solution Verified - Updated -

Issue

  • Upgrading Quay Operator does not upgrade Quay Registry automatically.
  • After upgrading Quay Operator, Quay registry UI shows the old version.
  • Quay registry upgrade fails with RouteComponentDependencyError error:

    2022-09-14T07:43:03.330566371Z 1.6631413833304935e+09    DEBUG    events    Warning    {"object": {"kind":"QuayRegistry","namespace":"quay","name":"quay","uid":"00000000-0000-0000-0000-000000000000","apiVersion":"quay.redhat.com/v1","resourceVersion":"635223928"}, "reason": "RouteComponentDependencyError", "message": "could not check for `Routes` API: dial tcp: lookup quay-test-route-quay.apps.example.local on 172.30.0.10:53: no such host"}
    

Environment

  • Red Hat Quay (Quay)
    • 3.6
  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content