-
Notifications
You must be signed in to change notification settings - Fork 1.1k
main: still rely on logrus (rather than using the internal log) #4804
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
main: still rely on logrus (rather than using the internal log) #4804
Conversation
This is a partial revert of 975ffc6, where we started using the internal log when the context is avaiable. It turns out that we missed a few pieces during the review, where we end up using the internal log without having the interceptors set up. This was raised by @haircommander during the review, we checked a few parts of the patch, but we still missed a few others. We can only use the internal logging after https://github.com/cri-o/cri-o/blob/d3dbaec060e33870e5cb5c3f7ec4207837804b00/cmd/crio/main.go#L222 happens. From this moment, we start having different ways of logging in the very same file and consistency becomes a problem then. With the consistency in mind, I'd like to **only** use logrus for debugging as part of this file. Note: This was noticed when debugging cri-o#4798 Signed-off-by: Fabiano Fidêncio <[email protected]>
|
@fidencio: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cc @saschagrunert |
Codecov Report
@@ Coverage Diff @@
## master #4804 +/- ##
==========================================
+ Coverage 43.00% 43.02% +0.02%
==========================================
Files 107 107
Lines 9791 9791
==========================================
+ Hits 4211 4213 +2
+ Misses 5130 5128 -2
Partials 450 450 |
|
/retest |
saschagrunert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/lgtm |
|
@haircommander: once the present PR merges, I will cherry-pick it on top of release-1.21 in a new PR and assign it to you. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fidencio, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@fidencio: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@haircommander: new pull request created: #4810 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This is a partial revert of 975ffc6,
where we started using the internal log when the context is avaiable.
It turns out that we missed a few pieces during the review, where we end
up using the internal log without having the interceptors set up. This
was raised by @haircommander during the review, we checked a few parts
of the patch, but we still missed a few others.
We can only use the internal logging after
cri-o/cmd/crio/main.go
Line 222 in d3dbaec
happens. From this moment, we start having different ways of logging in
the very same file and consistency becomes a problem then.
With the consistency in mind, I'd like to only use logrus for
debugging as part of this file.
Note: This was noticed when debugging
#4798
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
I think this one should also be backported to the
release-1.21branch,Does this PR introduce a user-facing change?