Skip to content

OCPQE-31553:adjust qe sa and permission test cases per new change#631

Open
kuiwang02 wants to merge 1 commit intoopenshift:mainfrom
kuiwang02:preflight
Open

OCPQE-31553:adjust qe sa and permission test cases per new change#631
kuiwang02 wants to merge 1 commit intoopenshift:mainfrom
kuiwang02:preflight

Conversation

@kuiwang02
Copy link
Contributor

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

Summary

This PR adjusts OLM v1 qe SA and preflight permission test cases per new change from boxcutterruntime, ensuring compatibility across all 4 environment combinations.

Besides them, it also enhance Makefile for make verify to report error and change fmt target from auto-fix to report error and provide how to fix. Or else, if the case owner forget to make correct format, tests-extension will not report error and pass the job. For example olmv1-singleownnamespace.go has format error and the tests-extension job of the PR which submit the code does not report error, but actualy the code is not good format. here, we enhance Makefile and correct it.

Environment Coverage

Env Preflight Boxcutter Status
Env1 ✅ Tested
Env2 ✅ Tested
Env3 ✅ Tested
Env4 ✅ Tested

assisted-by: Claude Code

@openshift-ci openshift-ci bot requested a review from bandrade February 5, 2026 05:49
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 5, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

@kuiwang02: This pull request references OCPQE-31553 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

Summary

This PR adjusts OLM v1 qe SA and preflight permission test cases per new change from boxcutterruntime, ensuring compatibility across all 4 environment combinations.

Besides them, it also enhance Makefile for make verify to report error and change fmt target from auto-fix to report error and provide how to fix. Or else, if the case owner forget to make correct format, tests-extension will not report error and pass the job. For example olmv1-singleownnamespace.go has format error and the tests-extension job of the PR which submit the code does not report error, but actualy the code is not good format. here, we enhance Makefile and correct it.

Environment Coverage

Env Preflight Boxcutter Status
Env1 ✅ Tested
Env2 ✅ Tested
Env3 ✅ Tested
Env4 ✅ Tested

assisted-by: Claude Code

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.

@kuiwang02
Copy link
Contributor Author

it is better to wait PR cluster-olm repo 163 to be merged and go into payload together.

@kuiwang02
Copy link
Contributor Author

/payload-job periodic-ci-openshift-operator-framework-operator-controller-release-4.22-periodics-e2e-aws-ovn-upi-extended-f2

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 5, 2026

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

  • periodic-ci-openshift-operator-framework-operator-controller-release-4.22-periodics-e2e-aws-ovn-upi-extended-f2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0099f4a0-0268-11f1-9cbe-1d1d9e4a5ae8-0

@kuiwang02 kuiwang02 force-pushed the preflight branch 3 times, most recently from b386507 to 8d65655 Compare February 10, 2026 00:44
@kuiwang02
Copy link
Contributor Author

/test openshift-e2e-aws

@kuiwang02
Copy link
Contributor Author

/test okd-scos-images

2 similar comments
@kuiwang02
Copy link
Contributor Author

/test okd-scos-images

@kuiwang02
Copy link
Contributor Author

/test okd-scos-images

@jianzhangbjz
Copy link
Member

openshift/cluster-olm-operator#163 has been merged.
/approve
/lgtm

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

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, kuiwang02

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 Feb 25, 2026
@kuiwang02
Copy link
Contributor Author

I will change the code per the upstream PR 2488.
/hold

@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 Feb 25, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

New changes are detected. LGTM label has been removed.

@kuiwang02
Copy link
Contributor Author

/hold

@kuiwang02
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

@kuiwang02: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-techpreview-olmv1-ext fa75110 link true /test e2e-aws-techpreview-olmv1-ext
ci/prow/e2e-gcp-ovn-upgrade fa75110 link true /test e2e-gcp-ovn-upgrade

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants