Skip to content

Conversation

@bandrade
Copy link

@bandrade bandrade commented Nov 18, 2025

Migrated three non-deprecated bandrade QE cases from openshift-tests-private into the OLMv1 test extension

@bandrade bandrade changed the title UPSTREAM: <carry>: migrate bandrade test cases to OTE OCPQE-30674: migrate bandrade's OLMv0 test cases to OTE Nov 18, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 18, 2025

@bandrade: This pull request references OCPQE-30674 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 sub-task to target the "4.21.0" version, but no target version was set.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 18, 2025

@bandrade: This pull request references OCPQE-30674 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

Migrated three non-deprecated bandrade QE cases from openshift-tests-private into the OLMv1 test extension

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.

@bandrade
Copy link
Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

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

  • periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/752fd5c0-c4d6-11f0-9dc9-3855e49f68ec-0

@bandrade
Copy link
Author

/assign @kuiwang02

@bandrade bandrade changed the title OCPQE-30674: migrate bandrade's OLMv0 test cases to OTE OCPQE-30674: migrate bandrade's OLMv1 test cases to OTE Nov 19, 2025
@kuiwang02
Copy link
Contributor

/payload-aggregate periodic-ci-openshift-operator-framework-operator-controller-release-4.21-periodics-e2e-aws-ovn-techpreview-extended-f1 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2025

@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.21-periodics-e2e-aws-ovn-techpreview-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a16773d0-c4e2-11f0-8b85-20f03a32c924-0

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 19, 2025
@jianzhangbjz
Copy link
Member

Hi @bandrade , this PR needs rebase.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 3, 2025
@bandrade
Copy link
Author

bandrade commented Dec 3, 2025

/payload-aggregate periodic-ci-openshift-operator-framework-operator-controller-release-4.21-periodics-e2e-aws-ovn-techpreview-extended-f1 5

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

@bandrade: 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.21-periodics-e2e-aws-ovn-techpreview-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4798c1b0-cfe1-11f0-9b28-6092e3961081-0

@jianzhangbjz
Copy link
Member

/payload-job aggregated-azure-ovn-upgrade-4.21-micro-release-openshift-release-analysis-aggregator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

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

@jianzhangbjz
Copy link
Member

/payload-job periodic-ci-openshift-operator-framework-operator-controller-release-4.21-periodics-e2e-aws-ovn-techpreview-extended-f1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

@jianzhangbjz: 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.21-periodics-e2e-aws-ovn-techpreview-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/514b94f0-d034-11f0-9779-54ff6a7777da-0

@jianzhangbjz
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

@bandrade: all tests passed!

Full PR test history. Your PR dashboard.

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.

@bandrade
Copy link
Author

bandrade commented Dec 4, 2025

Looks like we still meeds acknowledge-critical-fixes-only and verified labels.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants