Bug 1550372
Summary: | NFS volume recycle failed for ErrImagePull | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
Component: | Release | Assignee: | David Eads <deads> |
Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, aos-storage-staff, bchilds, bugzilla.com, byount, chrkim, fbrychta, hekumar, joelsmith, jokerman, jupierce, mmccomas, smunilla |
Target Milestone: | --- | ||
Target Release: | 3.9.0 | ||
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: | 2018-05-17 06:42:42 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: |
Description
Qin Ping
2018-03-01 06:26:10 UTC
Why the v1.9.1 for the image tag? The recycler was shipped with 3.9 with the tags listed here: https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/openshift3/ose-recycler (e.g. v3.9, v3.9.14) I see the same issue in our v3.9.14 instance. It's pulling ose-recycler:v1.9.1 for some reason. Is there any workaround for this? Can I update some template so It would be pulling ose-recycler:latest instead? It looks like it would require a change to the pod you are using - which is configured with controller arguments: https://docs.openshift.com/container-platform/3.6/architecture/additional_concepts/storage.html :latest should be relatively safe since I don't believe this image varies between releases. Verify this issue in OCP v3.9.20, still get the same error. The image tag v3.9.20 for one-recycler is exist, and the following command can be run successfully: docker pull registry.reg-aws.openshift.com:443/openshift3/ose-recycler:v3.9.20 Another workaround available to users is - defining environment variable: export OPENSHIFT_RECYCLER_IMAGE="openshift/origin-recycler:v3.9.0" or export OPENSHIFT_RECYCLER_IMAGE="openshift3/ose-recycler:v3.9.20" Opened a PR for fixing this in 3.9 so as users don't have to use environment variable - https://github.com/openshift/origin/pull/19374 v1.9.1 tag workaround works for me. Still need a real fix, for the PR is not merged, change the bug status to "ASSIGNED". Verified in OCP: oc v3.9.24 openshift v3.9.24 kubernetes v1.9.1+a0ce1bc657 # uname -a Linux host-172-16-120-35 3.10.0-693.21.1.el7.x86_64 #1 SMP Fri Feb 23 18:54:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1566 (In reply to Hemant Kumar from comment #14) > Another workaround available to users is - defining environment variable: > > export OPENSHIFT_RECYCLER_IMAGE="openshift/origin-recycler:v3.9.0" > > or > export OPENSHIFT_RECYCLER_IMAGE="openshift3/ose-recycler:v3.9.20" @Hemant does ones define this environment variable on every app node or what and with the root account or what? This should be defined on master node where controller manager runs. |