Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@fidencio
Copy link
Contributor

@fidencio fidencio commented Apr 26, 2021

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

grpc.StreamInterceptor(log.StreamInterceptor()),

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.21 branch,

Does this PR introduce a user-facing change?

None

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 fidencio requested review from mrunalp and runcom as code owners April 26, 2021 09:11
@openshift-ci-robot openshift-ci-robot added the release-note-none Denotes a PR that doesn't merit a release note. label Apr 26, 2021
@openshift-ci-robot
Copy link

@fidencio: The label(s) kind/bugr cannot be applied, because the repository doesn't have them.

Details

In response to this:

What type of PR is this?

/kind bugr

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

grpc.StreamInterceptor(log.StreamInterceptor()),

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.21 branch,

Does this PR introduce a user-facing change?

None

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.

@openshift-ci-robot openshift-ci-robot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Apr 26, 2021
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 26, 2021
@fidencio
Copy link
Contributor Author

/cc @saschagrunert

@codecov
Copy link

codecov bot commented Apr 26, 2021

Codecov Report

Merging #4804 (39c356c) into master (d3dbaec) will increase coverage by 0.02%.
The diff coverage is n/a.

❗ Current head 39c356c differs from pull request most recent head 33f2996. Consider uploading reports for the commit 33f2996 to get more accurate results

@@            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              

@fidencio
Copy link
Contributor Author

/retest

Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@haircommander
Copy link
Member

/lgtm
/cherry-pick release-1.21

@openshift-cherrypick-robot

@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.

Details

In response to this:

/lgtm
/cherry-pick release-1.21

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.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2021
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@fidencio
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

[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

Details Needs approval from an approver in each of these files:
  • OWNERS [fidencio,mrunalp,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mrunalp
Copy link
Member

mrunalp commented Apr 26, 2021

/lgtm

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 26, 2021

@fidencio: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/openshift-jenkins/e2e_crun_cgroupv2 33f2996 link /test e2e_cgroupv2

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e33ccae into cri-o:master Apr 26, 2021
@openshift-cherrypick-robot

@haircommander: new pull request created: #4810

Details

In response to this:

/lgtm
/cherry-pick release-1.21

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants