-
Notifications
You must be signed in to change notification settings - Fork 68
🐛 fix: boxcutter logging levels #2314
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
🐛 fix: boxcutter logging levels #2314
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
da24e61 to
423621d
Compare
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.
Pull Request Overview
This PR improves the logging strategy for the ClusterExtensionRevision controller by reducing verbosity and providing more actionable error messages. The changes shift detailed reconcile/teardown reports to debug-level logging while elevating validation and collision errors to error-level logging for better visibility.
- Changed successful reconcile/teardown reports from info-level to debug-level (V(1))
- Elevated preflight validation errors from info-level to error-level logging
- Enhanced error logging for reconcile/teardown failures to include report details when available
- Added phase context to validation and collision error messages
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
internal/operator-controller/controllers/clusterextensionrevision_controller.go
Outdated
Show resolved
Hide resolved
internal/operator-controller/controllers/clusterextensionrevision_controller.go
Outdated
Show resolved
Hide resolved
423621d to
2543dea
Compare
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.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2314 +/- ##
==========================================
+ Coverage 71.14% 74.19% +3.05%
==========================================
Files 91 91
Lines 7046 7054 +8
==========================================
+ Hits 5013 5234 +221
+ Misses 1618 1404 -214
- Partials 415 416 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| if rres != nil { | ||
| l.Error(err, "revision reconcile failed", "report", rres.String()) | ||
| } else { | ||
| l.Error(err, "revision reconcile failed") | ||
| } |
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 don't know if it's much of an improvement, but if we want to eliminate the duplication here we could do something like
| if rres != nil { | |
| l.Error(err, "revision reconcile failed", "report", rres.String()) | |
| } else { | |
| l.Error(err, "revision reconcile failed") | |
| } | |
| var kvs []string | |
| if rres != nil { | |
| kvs = append(kvs, "report", rres.String()) | |
| } | |
| l.Error(err, "revision reconcile failed", kvs...) |
or something like that
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.
Yep, we can done.
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.
We need keep the explicity approach otehrwise will fail in the lint; https://github.com/operator-framework/operator-controller/actions/runs/19230041339/job/54966203269?pr=2314
|
/lgtm - just left a small suggestion for possible improvement |
2543dea to
9f45e07
Compare
|
@perdasilva all done. |
- Use Error level for all error conditions (validation, collision, engine failures) - Move verbose success reports to V(1) debug mode - Include full diagnostic reports when errors occur
9f45e07 to
b621850
Compare
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.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: perdasilva 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 |
|
/override patch |
|
@tmshort: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. 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-sigs/prow repository. |
|
/override codecov/patch |
|
@tmshort: Overrode contexts on behalf of tmshort: codecov/patch 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-sigs/prow repository. |
d4e93be
into
operator-framework:main
c/c @jianzhangbjz @Xia-Zhao-rh