Skip to content

NO-ISSUE release-4.19 temporary fix for olm kustomization#6255

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
copejon:cherry-pick-c2d47ca-to-release-4.19
Feb 22, 2026
Merged

NO-ISSUE release-4.19 temporary fix for olm kustomization#6255
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
copejon:cherry-pick-c2d47ca-to-release-4.19

Conversation

@copejon
Copy link
Contributor

@copejon copejon commented Feb 20, 2026

Cherry-pick of commit c2d47ca from PR #6251.

Summary

Temporary fix for OLM kustomization that removes pprof-related YAML files.

Changes

  • Modified scripts/auto-rebase/rebase.sh to remove problematic pprof configuration files from OLM kustomization
  • This is a temporary workaround until the underlying issue is resolved

Testing

  • make test passed
  • ✅ Cherry-pick applied cleanly

Original commit by Pablo Acevedo Montserrat pacevedo@redhat.com

Made with Cursor

@coderabbitai
Copy link

coderabbitai bot commented Feb 20, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 20, 2026
@pacevedom
Copy link
Contributor

/override ci/prow/e2e-aws-tests ci/prow/e2e-aws-tests-arm ci/prow/e2e-aws-tests-bootc ci/prow/e2e-aws-tests-bootc-arm

Overriding so that next rebase does not have issues with optionals.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2026

@pacevedom: Overrode contexts on behalf of pacevedom: ci/prow/e2e-aws-tests, ci/prow/e2e-aws-tests-arm, ci/prow/e2e-aws-tests-bootc, ci/prow/e2e-aws-tests-bootc-arm

Details

In response to this:

/override ci/prow/e2e-aws-tests ci/prow/e2e-aws-tests-arm ci/prow/e2e-aws-tests-bootc ci/prow/e2e-aws-tests-bootc-arm

Overriding so that next rebase does not have issues with optionals.

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-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2026

@copejon: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 22, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, pacevedom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@pacevedom
Copy link
Contributor

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 22, 2026
@openshift-ci-robot
Copy link

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@pacevedom
Copy link
Contributor

/verified by CI

@openshift-ci-robot
Copy link

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 37749b1 into openshift:release-4.19 Feb 22, 2026
12 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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants