Installer fails to pull prometheus-operator image on OCP 3

Solution Verified - Updated -

Issue

Cluster installation fails at:

Failure summary:
  1. Hosts:    example.com
     Play:     Configure Cluster Monitoring Operator
     Task:     Wait for the ServiceMonitor CRD to be created
     Message:  non-zero return code

Events logs show it is trying to pull with incorrect registry/tag combination: *quay.io/coreos/prometheus-operator:v3.11.16*

$ oc get events -n openshift-monitoring
Events:
  Type     Reason          Age                 From                  Message
  ----     ------          ----                ----                  -------
  Normal   Scheduled       1h                  default-scheduler     Successfully assigned openshift-monitoring/prometheus-operator-6ff5f666bb-tfszb to example.com
  Normal   SandboxChanged  1h (x4 over 1h)     kubelet, example.com  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulling         1h (x3 over 1h)     kubelet, example.com  pulling image "quay.io/coreos/prometheus-operator:v3.11.16"
  Warning  Failed          1h (x3 over 1h)     kubelet, example.com  Error: ErrImagePull
  Warning  Failed          1h (x3 over 1h)     kubelet, example.com  Failed to pull image "quay.io/coreos/prometheus-operator:v3.11.16": rpc error: code = Unknown desc = Tag v3.11.16 not found in repository quay.io/coreos/prometheus-operator
  Normal   BackOff         59m (x193 over 1h)  kubelet, example.com  Back-off pulling image "quay.io/coreos/prometheus-operator:v3.11.16"
  Warning  Failed          39m (x277 over 1h)  kubelet, example.com  Error: ImagePullBackOff

Environment

Red Hat OpenShift Container Platform 3.11

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