Skip to content

Conversation

@sjenning
Copy link
Contributor

@sjenning sjenning commented Nov 30, 2020

@rphillips

#2211 did not change the log level for all platforms

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 30, 2020
Copy link
Contributor

Choose a reason for hiding this comment

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

adding a baremetal config?

@rphillips
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 30, 2020
@cgwalters
Copy link
Member

Ah yep, we still really need to de-dup the templates. Probably handle these explicitly in the code.

@cgwalters
Copy link
Member

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, rphillips, sjenning

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:

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

ExecStartPre=/bin/mkdir --parents /etc/kubernetes/manifests
ExecStartPre=/bin/rm -f /var/lib/kubelet/cpu_manager_state
Environment="KUBELET_LOG_LEVEL=4"
Environment="KUBELET_LOG_LEVEL=3"
Copy link

@darkmuggle darkmuggle Nov 30, 2020

Choose a reason for hiding this comment

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

Honest question: why not move this its own override to /etc/systemd/system/kubelet.service.d/kubelog.conf with

[Unit]
Environment="KUBELET_LOG_LEVEL=3"

That would set the log level in one stop.

@sjenning
Copy link
Contributor Author

/hold
might do what Ben suggests instead. @rphillips can you do that?

@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 Nov 30, 2020
@rphillips
Copy link
Contributor

yep... on it

@sjenning
Copy link
Contributor Author

close in favor of #2262

@sjenning sjenning closed this Nov 30, 2020
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants