Image-registry operator not available after RHOCP installation

Solution Verified - Updated -

Issue

  • After installation of RHOCP on Red Hat OpenStack Platform, the image-registry operator is not available.
$ oc get clusteroperator
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE
authentication                             4.5.6     True        False         False      38d
cloud-credential                           4.5.6     True        False         False      38d
cluster-autoscaler                         4.5.6     True        False         False      38d
config-operator                            4.5.6     True        False         False      38d
console                                    4.5.6     True        False         False      35d
csi-snapshot-controller                    4.5.6     True        False         False      35d
dns                                        4.5.6     True        False         False      38d
etcd                                       4.5.6     True        False         False      38d
image-registry
ingress                                    4.5.6     True        False         False      38d
insights                                   4.5.6     True        False         False      38d
kube-apiserver                             4.5.6     True        False         False      38d
kube-controller-manager                    4.5.6     True        False         False      38d
kube-scheduler                             4.5.6     True        False         False      38d
kube-storage-version-migrator              4.5.6     True        False         False      35d
machine-api                                4.5.6     True        False         False      38d
machine-approver                           4.5.6     True        False         False      38d
machine-config                             4.5.6     True        False         False      35d
marketplace                                4.5.6     True        False         False      35d
monitoring                                 4.5.6     True        False         False      38d
network                                    4.5.6     True        False         False      38d
node-tuning                                4.5.6     True        False         False      38d
openshift-apiserver                        4.5.6     True        False         False      38d
openshift-controller-manager               4.5.6     True        False         False      38d
openshift-samples                          4.5.6     True        False         False      38d
operator-lifecycle-manager                 4.5.6     True        False         False      38d
operator-lifecycle-manager-catalog         4.5.6     True        False         False      38d
operator-lifecycle-manager-packageserver   4.5.6     True        False         False      35d
service-ca                                 4.5.6     True        False         False      38d
storage                                    4.5.6     True        False         False      38d
  • Check image-registry pod logs.
$ oc logs cluster-image-registry-operator-xxxx
E1020 06:54:06.631909      13 nodecadaemon.go:82] NodeCADaemonController: unable to sync: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.631932      13 clusteroperator.go:96] unable to sync ClusterOperatorStatusController: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
I1020 06:54:06.631978      13 caconfig.go:75] unable to get the service name to add service-ca.crt
E1020 06:54:06.632063      13 imageregistrycertificates.go:94] ImageRegistryCertificatesController: unable to sync: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.636007      13 imageconfig.go:109] ImageConfigController: unable to sync: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.637069      13 nodecadaemon.go:82] NodeCADaemonController: unable to sync: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.637072      13 clusteroperator.go:96] unable to sync ClusterOperatorStatusController: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.660002      13 controllerimagepruner.go:306] (image pruner) unable to sync: unable to apply objects: failed to create object *v1beta1.CronJob, Namespace=openshift-image-registry, Name=image-pruner: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E1020 06:54:06.660391      13 controller.go:311] unable to sync: Failed to authenticate provider client: Post https://X.X.X.X:YYYY//v3/auth/tokens: x509: certificate signed by unknown authority, requeuing
E1020 06:54:06.667932      13 clusteroperator.go:96] unable to sync ClusterOperatorStatusController: config.imageregistry.operator.openshift.io "cluster" not found, requeuing

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.5
  • Red Hat OpenStack Platform

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