Bug 1976293 - [backport 4.6]Evidence of disconnected installs pulling images from the local registry instead of quay.io
Summary: [backport 4.6]Evidence of disconnected installs pulling images from the local...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.4
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: 4.6.z
Assignee: Qi Wang
QA Contact: MinLi
URL:
Whiteboard:
Depends On: 1881694
Blocks: 1976297
TreeView+ depends on / blocked
 
Reported: 2021-06-25 17:38 UTC by Qi Wang
Modified: 2021-07-14 07:17 UTC (History)
8 users (show)

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.
Clone Of: 1881694
: 1976297 (view as bug list)
Environment:
Last Closed: 2021-07-14 07:16:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cri-o cri-o pull 5056 0 None open [release-1.19] Bug 1881694: Add pull source as info level log 2021-07-01 17:39:41 UTC
Red Hat Product Errata RHBA-2021:2641 0 None None None 2021-07-14 07:17:12 UTC

Comment 1 Qi Wang 2021-06-25 17:39:17 UTC 
Backport bug https://bugzilla.redhat.com/show_bug.cgi?id=1881694 for 4.6.
Comment 3 Qi Wang 2021-06-25 18:20:06 UTC 
Tag 4.6.z according to #comment2
Comment 7 MinLi 2021-07-09 07:13:52 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
Comment 9 errata-xmlrpc 2021-07-14 07:16:58 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.