New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-1.20] Bug 1881694 Add pull source as info level log #4536
[release-1.20] Bug 1881694 Add pull source as info level log #4536
Conversation
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1881694 This BZ needs change the log level of the image pull location from the debug to info. Crio could use SystemContext.DockerLogPullSource to log the physical image source if it's from a mirror. Signed-off-by: Qi Wang <qiwan@redhat.com>
|
/retest |
Codecov Report
@@ Coverage Diff @@
## release-1.20 #4536 +/- ##
================================================
- Coverage 40.54% 40.50% -0.05%
================================================
Files 117 117
Lines 9422 9434 +12
================================================
+ Hits 3820 3821 +1
- Misses 5173 5183 +10
- Partials 429 430 +1 |
|
/approve LGTM |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, QiWang19 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/test integration_crun |
|
/test integration_fedora |
Signed-off-by: Qi Wang qiwan@redhat.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1881694
This BZ needs change the log level of the image pull location from the debug to info.
Crio could use SystemContext.DockerLogPullSource to log the physical image source if it's from a mirror.
Which issue(s) this PR fixes:
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1881694
Special notes for your reviewer:
Does this PR introduce a user-facing change?