Skip to content

Conversation

@camilamacedo86
Copy link
Contributor

@camilamacedo86 camilamacedo86 commented Nov 8, 2025

  • 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

c/c @jianzhangbjz @Xia-Zhao-rh

Copilot AI review requested due to automatic review settings November 8, 2025 23:16
@camilamacedo86 camilamacedo86 requested a review from a team as a code owner November 8, 2025 23:16
@netlify
Copy link

netlify bot commented Nov 8, 2025

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit b621850
🔍 Latest deploy log https://app.netlify.com/projects/olmv1/deploys/6911d67d3d98c300077c02b4
😎 Deploy Preview https://deploy-preview-2314--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@camilamacedo86 camilamacedo86 changed the title 🐛 (fix): boxcutter logging 🐛 fix: improve boxcutter logging levels Nov 8, 2025
Copy link

Copilot AI left a 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.

Copy link

Copilot AI left a 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
Copy link

codecov bot commented Nov 8, 2025

Codecov Report

❌ Patch coverage is 53.84615% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.19%. Comparing base (b3f85d5) to head (b621850).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...controllers/clusterextensionrevision_controller.go 53.84% 3 Missing and 3 partials ⚠️
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     
Flag Coverage Δ
e2e 45.80% <0.00%> (-0.14%) ⬇️
experimental-e2e 48.19% <38.46%> (?)
unit 58.53% <38.46%> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@camilamacedo86 camilamacedo86 changed the title 🐛 fix: improve boxcutter logging levels 🐛 fix: boxcutter logging levels Nov 8, 2025
Comment on lines +152 to +156
if rres != nil {
l.Error(err, "revision reconcile failed", "report", rres.String())
} else {
l.Error(err, "revision reconcile failed")
}
Copy link
Contributor

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

Suggested change
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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, we can done.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@perdasilva
Copy link
Contributor

/lgtm - just left a small suggestion for possible improvement

@camilamacedo86
Copy link
Contributor Author

@perdasilva all done.
So, I think this small one can fly :-)

- 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
Copilot AI review requested due to automatic review settings November 10, 2025 12:11
Copy link

Copilot AI left a 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.

@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 10, 2025
@tmshort
Copy link
Contributor

tmshort commented Nov 10, 2025

/override patch

@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2025

@tmshort: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • patch

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • codecov/patch
  • crd-diff
  • e2e-kind
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • tide
  • unit-test-basic
  • upgrade-e2e
  • verify

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:

/override patch

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.

@tmshort
Copy link
Contributor

tmshort commented Nov 10, 2025

/override codecov/patch

@openshift-ci
Copy link

openshift-ci bot commented Nov 10, 2025

@tmshort: Overrode contexts on behalf of tmshort: codecov/patch

In response to this:

/override codecov/patch

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.

@openshift-merge-bot openshift-merge-bot bot merged commit d4e93be into operator-framework:main Nov 10, 2025
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants