Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bug 1828622: bumps kubelet log level to 4 #1672

Merged
merged 1 commit into from
Apr 28, 2020
Merged

Bug 1828622: bumps kubelet log level to 4 #1672

merged 1 commit into from
Apr 28, 2020

Conversation

rphillips
Copy link
Contributor

- What I did
Bumping the kubelet log level to 4 to aid in debugging an issue.

- How to verify it

- Description for the changelog

@rphillips rphillips changed the title bumps kubelet log level to 4 WIP: bumps kubelet log level to 4 Apr 22, 2020
@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 22, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 22, 2020
@tedyu
Copy link

tedyu commented Apr 23, 2020

Makes sense.
This should give us more information for debugging.

@rphillips rphillips closed this Apr 25, 2020
@rphillips rphillips changed the title WIP: bumps kubelet log level to 4 bumps kubelet log level to 4 Apr 27, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 27, 2020
@rphillips rphillips reopened this Apr 27, 2020
@rphillips
Copy link
Contributor Author

/hold cancel

merging this PR to bump the log level to 4 will give us more insight into CI issues

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 27, 2020
@mrunalp
Copy link
Member

mrunalp commented Apr 27, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 27, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrunalp, rphillips

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

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

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@rphillips rphillips changed the title bumps kubelet log level to 4 Bug 1828622: bumps kubelet log level to 4 Apr 27, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. label Apr 27, 2020
@openshift-ci-robot
Copy link
Contributor

@rphillips: This pull request references Bugzilla bug 1828622, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1828622: bumps kubelet log level to 4

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 bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 27, 2020
@rphillips
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 27, 2020
@openshift-ci-robot
Copy link
Contributor

@rphillips: This pull request references Bugzilla bug 1828622, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

/bugzilla refresh

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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 27, 2020
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 28, 2020 •
edited
Loading

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

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 bb3b748 link /test e2e-aws-scaleup-rhel7

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit b6d9a20 into openshift:master Apr 28, 2020
@openshift-ci-robot
Copy link
Contributor

@rphillips: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1672. Bugzilla bug 1828622 has been moved to the MODIFIED state.

In response to this:

Bug 1828622: bumps kubelet log level to 4

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.

kikisdeliveryservice added a commit to kikisdeliveryservice/machine-config-operator that referenced this pull request Nov 9, 2020
@kikisdeliveryservice
Drop kubelet logging back down to level 3
78417c6 
KUBELET_LOG_LEVEL was bumped to level 4 to aid in
debugging some issue by node team (see openshift#1672).
However customers upgrading to 4.5 in prod, are seeing this bump
causing extra GBs of data to be saved.

Closes: BZ 1895385
@kikisdeliveryservice kikisdeliveryservice mentioned this pull request Nov 9, 2020
Merged
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/machine-config-operator that referenced this pull request Nov 10, 2020
@kikisdeliveryservice
Drop kubelet logging back down to level 3
5a61ef9 
KUBELET_LOG_LEVEL was bumped to level 4 to aid in
debugging some issue by node team (see openshift#1672).
However customers upgrading to 4.5 in prod, are seeing this bump
causing extra GBs of data to be saved.

Closes: BZ 1895385
rphillips pushed a commit to rphillips/machine-config-operator that referenced this pull request Nov 19, 2020
@kikisdeliveryservice @rphillips
Drop kubelet logging back down to level 3
1ec49e0 
KUBELET_LOG_LEVEL was bumped to level 4 to aid in
debugging some issue by node team (see openshift#1672).
However customers upgrading to 4.5 in prod, are seeing this bump
causing extra GBs of data to be saved.

Closes: BZ 1895385
tsorya pushed a commit to tsorya/machine-config-operator that referenced this pull request Nov 24, 2020
@kikisdeliveryservice @tsorya
Drop kubelet logging back down to level 3
7a41295 
KUBELET_LOG_LEVEL was bumped to level 4 to aid in
debugging some issue by node team (see openshift#1672).
However customers upgrading to 4.5 in prod, are seeing this bump
causing extra GBs of data to be saved.

Closes: BZ 1895385
rphillips added a commit to rphillips/machine-config-operator that referenced this pull request Dec 4, 2020
@rphillips
Drop kubelet logging back down to level 3
cf4c735 
KUBELET_LOG_LEVEL was bumped to level 4 to aid in
debugging some issue by node team (see openshift#1672).
However customers upgrading to 4.5 in prod, are seeing this bump
causing extra GBs of data to be saved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mrunalp mrunalp Awaiting requested review from mrunalp

@sjenning sjenning Awaiting requested review from sjenning

Assignees

@mrunalp mrunalp

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@rphillips @tedyu @mrunalp @openshift-ci-robot @openshift-bot @openshift-merge-robot