OCPBUGS-72591: Lower verbosity for parseIPList empty list logging#709
Conversation
Since it's impossible to distinguish between an unset value and a value set as empty, we prefer to lower the verbosity from V(0) to V(7) to reduce unnecessary logging.
|
@alebedev87: This pull request references Jira Issue OCPBUGS-72591, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@alebedev87: This pull request references Jira Issue OCPBUGS-72591, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/assign |
|
/approve Do we document the various log levels anywhere? It would be useful to have some guidance for both developers and end users, to help everyone understand in general terms what gets logged (or should be logged) at a given log level. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah 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 |
|
/lgtm |
|
Tested it with 4.22.0-0-2026-01-23-022622-test-ci-ln-lnmj02t-latest Could see the parseIPList log in 4.22.0-0.nightly-2026-01-22-122134 |
|
/label qe-approved |
|
@alebedev87: This pull request references Jira Issue OCPBUGS-72591, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@ShudiLi: This PR has been marked as verified by 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@alebedev87: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
|
@alebedev87: Jira Issue Verification Checks: Jira Issue OCPBUGS-72591 Jira Issue OCPBUGS-72591 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-01-24-213011 |
|
/cherry-pick release-4.21 |
|
@alebedev87: new pull request created: #752 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-sigs/prow repository. |
Since it's impossible to distinguish between an unset value and a value set as empty, we prefer to lower the verbosity from V(0) to V(7) to reduce unnecessary logging.