Skip to content

OPRUN-4440,OPRUN-4230: Enable Boxcutter in TPNU#163

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
perdasilva:olmv1-boxcutter-tp
Feb 24, 2026
Merged

OPRUN-4440,OPRUN-4230: Enable Boxcutter in TPNU#163
openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
perdasilva:olmv1-boxcutter-tp

Conversation

@perdasilva
Copy link

@perdasilva perdasilva commented Jan 19, 2026

This PR enables Boxcutter in TechPreviewNoUpgrade. The following changes are made:

  • Bumps openshift/api dependency to pull in Boxcutter flag
  • Bumps openshift/client-go to make the build build
  • Adds the BoxcutterRuntime feature gate mapping
  • Updates the incompatible operator controller to check for olm.properties in the latest active ClusterExtensionRevision if the boxcutter FG is turned on
  • Adds some unit tests around the sync method for the incompatible operator controller for sanity

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@perdasilva perdasilva changed the title Olmv1 boxcutter tp Bump openshift-api and add BoxcutterRuntime FG mapping Jan 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 2026

[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

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 19, 2026
@perdasilva perdasilva marked this pull request as ready for review January 21, 2026 14:10
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 21, 2026
@perdasilva
Copy link
Author

/hold for testing

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2026
@openshift-ci openshift-ci bot requested review from anik120 and oceanc80 January 21, 2026 14:11
@perdasilva
Copy link
Author

/testwith openshift/api#2659

@camilamacedo86
Copy link

/testwith #163 openshift/api#2659

@camilamacedo86
Copy link

/testwith openshift/operator-framework-operator-controller/main/ci/prow/tests-extension openshift/operator-framework-operator-controller#410 openshift/release#67233

Should fail just to test if testwih works here

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@camilamacedo86, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/operator-framework-operator-controller/main/ci/prow/tests-extension

@perdasilva
Copy link
Author

/testwith openshift/operator-framework-operator-controller/main/ci/prow/tests-extension openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/operator-framework-operator-controller/main/ci/prow/tests-extension

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator/main/ci/prow/openshift-e2e-aws-techpreview openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/cluster-olm-operator/main/ci/prow/openshift-e2e-aws-techpreview

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/cluster-olm-operator

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator/main openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/cluster-olm-operator/main

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator/main/openshift-e2e-techpreview openshift#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: invalid format for additional PR: openshift#2659

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator/main/openshift-e2e-techpreview openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: could not generate prow job. ERROR:

BUG: test 'openshift-e2e-techpreview' not found in injected config

@perdasilva
Copy link
Author

/testwith openshift/cluster-olm-operator/main/ci/prow/openshift-e2e-techpreview openshift/api#2659

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@perdasilva, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: openshift/cluster-olm-operator/main/ci/prow/openshift-e2e-techpreview

@perdasilva
Copy link
Author

/test lint

Per Goncalves da Silva added 3 commits February 12, 2026 10:17
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@perdasilva
Copy link
Author

/retest

@perdasilva
Copy link
Author

/test openshift-e2e-aws-devpreview

1 similar comment
@perdasilva
Copy link
Author

/test openshift-e2e-aws-devpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

@perdasilva: 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.

@perdasilva
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/edbb67e0-0cd7-11f1-937a-123531a1c2ab-0

@perdasilva
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2026

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/39afa230-1091-11f1-8db9-4cf0264d5bf0-0

@perdasilva
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2026

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4345b460-1091-11f1-94dd-e06f1716310b-0

@perdasilva
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2026

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a18482d0-10bf-11f1-97b6-26650d3ef05d-0

@perdasilva
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 24, 2026

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.22-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/19337400-1159-11f1-9a3e-b265f4ecd00e-0

@perdasilva
Copy link
Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 24, 2026
Copy link

@pedjak pedjak left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2026
@bandrade
Copy link

/label qe-approved
/verified by @bandrade

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

@bandrade: This PR has been marked as verified by @bandrade.

Details

In response to this:

/label qe-approved
/verified by @bandrade

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-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 24, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 24, 2026

@perdasilva: This pull request references OPRUN-4440 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

This pull request references OPRUN-4230 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR enables Boxcutter in TechPreviewNoUpgrade. The following changes are made:

  • Bumps openshift/api dependency to pull in Boxcutter flag
  • Bumps openshift/client-go to make the build build
  • Adds the BoxcutterRuntime feature gate mapping
  • Updates the incompatible operator controller to check for olm.properties in the latest active ClusterExtensionRevision if the boxcutter FG is turned on
  • Adds some unit tests around the sync method for the incompatible operator controller for sanity

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 bbd8f9d into openshift:main Feb 24, 2026
11 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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants