-
Notifications
You must be signed in to change notification settings - Fork 462
cmd: Configure klog to match glog #1730
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
Conversation
d5a2bd4 to
dd9cfe0
Compare
2ffa0f6 to
86de0f2
Compare
|
Repurposed this branch to just be about klog/glog compat. This gives us the ability to use I also drop some flag parsing which had been used by |
Following [1,2]. This gives us the ability to use -v=10 when calling our executables and get all of the klog goodness out of our vendored Kubernetes libraries. I also drop some flag parsing which had been used by 'version' commands which print the version and exist, and so never actually needed the logging stack to be configured. [1]: https://github.com/kubernetes/klog#coexisting-with-glog [2]: https://github.com/kubernetes/klog/blob/a5796cb0e98abe2d0500974a80ec960af26cfd93/examples/coexist_glog/coexist_glog.go
86de0f2 to
5d4d256
Compare
|
rhel7 job failed, but shows that MCD logs still have the |
cgwalters
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.
I am not intimately familiar with glog vs klog, this overall looks like a nice cleanup though!
Adding 4.7 label.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, wking 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 |
|
@wking: The following tests 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. |
|
@wking: The following tests 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. 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. |
To try and understand why compute nodes sometimes have a long delay between informer initialization and the initial MachineConfig retrieval in getStateAndConfigs.
https://bugzilla.redhat.com/show_bug.cgi?id=1834895