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
OCPBUGS-29919: Decrease log level when detecting node IP #301
Conversation
@mkowalski: This pull request references Jira Issue OCPBUGS-29919, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@mkowalski: This pull request references Jira Issue OCPBUGS-29919, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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 openshift-eng/jira-lifecycle-plugin repository. |
/cc @cybertron |
/retest-required |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cybertron, mkowalski 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 |
/retest-required
|
/retest-required
|
/test images |
1 similar comment
/test images |
@mkowalski: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
/test images |
/test e2e-metal-ipi-ovn-ipv6 |
a77854c
into
openshift:master
@mkowalski: Jira Issue OCPBUGS-29919: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-29919 has not been moved to the MODIFIED state. In 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 openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-baremetal-runtimecfg-container-v4.16.0-202404050813.p0.ga77854c.assembly.stream.el9 for distgit baremetal-runtimecfg. |
/cherry-pick release-4.15 |
@mkowalski: new pull request created: #304 In 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. |
/jira-refresh |
/jira refresh |
@mkowalski: Jira Issue OCPBUGS-29919 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. In 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira-refresh |
/jira refresh |
@zhaozhanqi: Jira Issue OCPBUGS-29919: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-29919 has been moved to the MODIFIED state. In 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 openshift-eng/jira-lifecycle-plugin repository. |
In openshift#301 we have decreased level from INFO to DEBUG for multiple messages around Node IP detection logic. However, we never implemented ability to enable DEBUG level so that those logs were effectively unreachable. With this PR we will consume `ENABLE_NODEIP_DEBUG` env variable and if configured, we will increase log level. For OpenShift customers the variable will be consumed via ConfigMap as defined in the respective Pod manifest in the MCO repository. Fixes: OCPBUGS-32348
In openshift#301 we have decreased level from INFO to DEBUG for multiple messages around Node IP detection logic. However, we never implemented ability to enable DEBUG level so that those logs were effectively unreachable. With this PR we will consume `ENABLE_NODEIP_DEBUG` env variable and if configured, we will increase log level. For OpenShift customers the variable will be consumed via ConfigMap as defined in the respective Pod manifest in the MCO repository. Fixes: OCPBUGS-32348
No description provided.