-
Notifications
You must be signed in to change notification settings - Fork 150
CONSOLE-1523: Change log level values to use klog types #250
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
|
/assign @jhadvig |
|
/hold |
|
/retest |
|
@zherman0 this one has sat for a bit, finally getting the open PRs list down enough to take a look. Is there a matching console PR? I assume both need to change at more or less the same time. Or does the console have some logic to ensure we don't get in a bad state due to flag mismatch? |
|
Button click misfire :) |
|
@benjaminapetersen @spadgett - There is a a corresponding console PR: openshift/console#1862 |
|
@zherman0 so the Curious, do you need the kubernetes component base? I'm guessing thats why the PR blew up. |
benjaminapetersen
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.
Hasn't quite got the correct flags yet.
|
For log level values, I am using this doc: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md |
benjaminapetersen
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.
Need the correct flag here.
| switch logLevel { | ||
| case operatorv1.Normal: | ||
| flag = "--log-level=*=NOTICE" | ||
| flag = "--log-level=2" |
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.
These are still
--log-level=2
But we need to update to
-v=2
Wrong flag.
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 leaving this like this for now since console can handle the old values. We will get console portion merged first and then update this. I will update the code but I want to make sure this does not get merged.
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.
This PR won't merge until the -v flag is updated, so you should be safe. Definitely free to do whatever locally, but I would prob push the correct code up for the open PR.
| flag := "" | ||
| // Since the console-operator logging has different logging levels then the capnslog, | ||
| // that we use for console server(bridge) we need to map them to each other | ||
| // console server(bridge) expects flag log-level |
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.
This comment can go away, it will no longer expect log-level after these merge.
|
/retest |
|
/retest |
|
/test e2e-aws-operator |
|
@zherman0: 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. |
jhadvig
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.
Aligning to the values that we are using in the Console's Switch to klog PR
| case operatorv1.Trace: | ||
| flag = "-v=4" | ||
| case operatorv1.TraceAll: | ||
| flag = "-v=5" |
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.
| flag = "-v=5" | |
| flag = "-v=10" |
| flag = "--log-level=*=DEBUG" | ||
| case operatorv1.Trace, operatorv1.TraceAll: | ||
| flag = "--log-level=*=TRACE" | ||
| flag = "-v=3" |
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.
| flag = "-v=3" | |
| flag = "-v=4" |
| flag = "--log-level=*=TRACE" | ||
| flag = "-v=3" | ||
| case operatorv1.Trace: | ||
| flag = "-v=4" |
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.
| flag = "-v=4" | |
| flag = "-v=6" |
|
/retest |
|
/assign @yapei @ahardin-rh @sferich888 This is ready to test. @jhadvig @zherman0 I assume this should be tested with openshift/console#1862 together using cluster-bot? |
spadgett
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.
/approve
|
@spadgett was successfully able to launch a cluster using cluster with combination of both PRs. Checked if the |
|
/label qe-approved |
|
@yapei: 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. |
|
Launched cluster |
|
/lgtm |
|
@ahardin-rh do we have a corresponding docs PR to link this to? That shows users how to manipulate this? |
|
@zherman0: 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. |
|
/hold cancel |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhadvig, spadgett, yapei, zherman0 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 |
|
@ahardin-rh could you please respond to #250 (comment) . Thanks ! :) |



This changes the capnslog values to accepted klog log level values. I have just converted them as best I can but we might want to re-evaluate what each maps to.
CONSOLE-1523