Bug 1976293
| Summary: | [backport 4.6]Evidence of disconnected installs pulling images from the local registry instead of quay.io | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qi Wang <qiwan> | |
| Component: | Node | Assignee: | Qi Wang <qiwan> | |
| Node sub component: | CRI-O | QA Contact: | MinLi <minmli> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | medium | CC: | aos-bugs, dwalsh, jokerman, minmli, nagrawal, scuppett, tsweeney, umohnani | |
| Version: | 4.4 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.6.z | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: |
Cause: Crio logs has no information about the pull source
Consequence: Failed to tell if the image was pulled from the registry mirror.
Fix: Added info level log information to crio about the pull source of the image.
Result: The physical pull source can be shown in the info level log.
|
Story Points: | --- | |
| Clone Of: | 1881694 | |||
| : | 1976297 (view as bug list) | Environment: | ||
| Last Closed: | 2021-07-14 07:16:58 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1881694 | |||
| Bug Blocks: | 1976297 | |||
|
Comment 1
Qi Wang
2021-06-25 17:39:17 UTC
verified on version: 4.6.0-0.nightly-2021-07-07-181104 sh-4.4# crictl version Version: 0.1.0 RuntimeName: cri-o RuntimeVersion: 1.19.2-7.rhaos4.6.git9ab5342.el8 RuntimeApiVersion: v1alpha1 Jul 09 07:04:05 minmli-070801-rl2s5-compute-1 crio[1599]: time="2021-07-09 07:04:05.453050715Z" level=info msg="Checking image status: upshift.mirror-registry.e.devcluster.openshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4" id=077716ef-306c-452b-a053-b7b92fa94bd name=/runtime.v1alpha2.ImageService/ImageStatus Jul 09 07:04:05 minmli-070801-rl2s5-compute-1 crio[1599]: time="2021-07-09 07:04:05.453457402Z" level=info msg="Image upshift.mirror-registry.qe.devcluster.opeshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4 not found" id=077716ef-306c-452b-a053-b7b92f9a94bd ame=/runtime.v1alpha2.ImageService/ImageStatus Jul 09 07:04:05 minmli-070801-rl2s5-compute-1 crio[1599]: time="2021-07-09 07:04:05.454324428Z" level=info msg="Pulling image: upshift.mirror-registry.qe.devclster.openshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4" id=9f40dfe7-6434-4930-96c1-e5c07002267f nme=/runtime.v1alpha2.ImageService/PullImage evcluster.openshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4\""ccess \"upshift.mirror-registry.qe.Jul 09 07:04:05 minmli-070801-rl2s5-compute-1 crio[1599]: time="2021-07-09 07:04:05.484522925Z" level=info msg="Trying to access \"upshift.mirror-registry.qe.evcluster.openshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4\"" Jul 09 07:04:16 minmli-070801-rl2s5-compute-1 crio[1599]: time="2021-07-09 07:04:16.452990475Z" level=info msg="Pulled image: upshift.mirror-registry.qe.devcluster.openshift.com:5001/rhscl/ruby-27-rhel7@sha256:2b41ad8a4d55e3cc7f84a124a2fef680bee6157d8dbe6d6dc1528bc482d979a4" id=9f40dfe7-6434-4930-96c1-e5c07002267f name=/runtime.v1alpha2.ImageService/PullImage 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 (OpenShift Container Platform 4.6.38 bug fix update), 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-2021:2641 |