Bug 2119493
| Summary: | enable-odf-console-plugin job imagepullbackoff if image registry not deployed | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Dale Bewley <dbewley> |
| Component: | management-console | Assignee: | Nishanth Thomas <nthomas> |
| Status: | CLOSED NOTABUG | QA Contact: | Prasad Desala <tdesala> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | badhikar, jefbrown, jrivera, madam, muagarwa, nthomas, ocs-bugs, odf-bz-bot |
| Target Milestone: | --- | Flags: | sheggodu:
needinfo?
(nthomas) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-03 15:15:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Confirmed same behavior on OCP 4.10.26 fresh install. ODF Operator does not have a job that it relies on. Is this job created by you? Sorry for the false report. It turns out the job was created by gitops-catalog kustomization. https://github.com/redhat-cop/gitops-catalog/blob/main/openshift-data-foundation-operator/operator/base/enable-console-plugin-job.yaml |
Description of problem (please be detailed as possible and provide log snippests): The enable-odf-console-plugin job has an image pullspec that references the cluster registry. In cases where cluster image regsitry does not exist the ODF console plugin will not be enabled. oc get pods -l job-name=enable-odf-console-plugin -n openshift-storage NAME READY STATUS RESTARTS AGE enable-odf-console-plugin-r7dtk 0/1 ImagePullBackOff 0 17h oc get job/enable-odf-console-plugin -n openshift-storage \ -o jsonpath='{.spec.template.spec.containers[*].image}' image-registry.openshift-image-registry.svc:5000/openshift/cli oc get pods -n openshift-storage -o json | jq '.items[].spec.containers[].image' "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:3658954f199040b0f244945c94955f794ee68008657421002e1b32962e7c30fc" "registry.redhat.io/odf4/odf-csi-addons-rhel8-operator@sha256:83b24d46f98858fd9d7a7545f4e1b0bdd810b3e4c615ec6f8d46a51bf5ab003a" "image-registry.openshift-image-registry.svc:5000/openshift/cli" "registry.redhat.io/odf4/mcg-rhel8-operator@sha256:84a562d0337bbac13c098bee7eb29f383d2e1b019b2d8fc823e68b19ce41be60" "registry.redhat.io/odf4/ocs-rhel8-operator@sha256:cdd4838430fde2c9fcec7cd37429c2cc99c8f4bbdc27e4069f8abe4bff88498f" "registry.redhat.io/odf4/ocs-rhel8-operator@sha256:cdd4838430fde2c9fcec7cd37429c2cc99c8f4bbdc27e4069f8abe4bff88498f" "registry.redhat.io/odf4/odf-console-rhel8@sha256:e61cb3f5c56771f94b6c80a99c644be560b1b5569d9fac7b5cc2860edb00e0b8" "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:3658954f199040b0f244945c94955f794ee68008657421002e1b32962e7c30fc" "registry.redhat.io/odf4/odf-rhel8-operator@sha256:7473ccb3651cda84119af3f73bc05d9634f7999461d7fca1ded03f067a942238" "registry.redhat.io/odf4/rook-ceph-rhel8-operator@sha256:dfe11ebccdc711a0b303d78c93998dac5fa41e8946beb7536b8a5e42c6d9ad05" Version of all relevant components (if applicable): - OCP 4.11.0 vSphere IPI deploymnet - ODF 4.10.5 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Causes confusion in a new deployment when it would appear ODF has no mgmt console. Is there any workaround available to the best of your knowledge? - Deploy registry and wait for job to reconcile. - Or updated job image pull spec to registry.access.redhat.com/openshift4/ose-cli Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes. Can this issue reproduce from the UI? No. If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install ODF to a platform lacking a cluster registry by default. 2. 3. Actual results: No console plugin enabled Expected results: ODF console plugin enabled Additional info: