OpenShift Registry Console image not upgraded during 3.9 patch level upgrade

Solution In Progress - Updated -

Issue

After executing the Ansible Playbook to upgrade my OpenShift cluster to a later 3.9 version, for example from 3.9.31 to 3.9.33, my Registry Console image version remains tagged as v3.9 although my other images are at the later version, e.g. v3.9.33:

$ oc status
In project default on server https://openshift.internal.otto39.lab.rdu2.cee.redhat.com:443

https://docker-registry-default.apps.otto39.lab.rdu2.cee.redhat.com (passthrough) (svc/docker-registry)
  dc/docker-registry deploys docker.io/openshift3/ose-docker-registry:v3.9.33 
    deployment #1 deployed 11 days ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443, 53->8053, 53->8053

https://registry-console-default.apps.otto39.lab.rdu2.cee.redhat.com (passthrough) (svc/registry-console)
  dc/registry-console deploys registry.access.redhat.com/openshift3/registry-console:v3.9 
    deployment #1 deployed 11 days ago - 1 pod

svc/router - 172.30.251.58 ports 80, 443, 1936
  dc/router deploys docker.io/openshift3/ose-haproxy-router:v3.9.33 
    deployment #1 deployed 11 days ago - 1 pod

Note that the Registry Console is always tagged as v3.9. To see the actual image version one must use "docker images" and this will reveal that the Registry Console image remains at the same version it was before the upgrade.

Environment

  • Red Hat OpenShift Container Platform
    • 3.9

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.