Skip to content

OCPQE-29415:add OTE into olmv0 with new location#1108

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kuiwang02:fixsync
Sep 17, 2025
Merged

OCPQE-29415:add OTE into olmv0 with new location#1108
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kuiwang02:fixsync

Conversation

@kuiwang02
Copy link
Copy Markdown
Contributor

/cc @perdasilva @jianzhangbjz

I am sorry the auto-sync is broken after #1105 is merged.
Per https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-auto-olm-downstreaming/1967740380359168000, it treats tests-extension as repo if I put it under staging directory.

so, I change the tests-extension location to fix auto-sync.

@kuiwang02
Copy link
Copy Markdown
Contributor Author

kuiwang02 commented Sep 16, 2025

/retitle OCPQE-29415:change ote location to fix auto-sync

@openshift-ci openshift-ci Bot changed the title change ote location to fix auto-sync OCPQE-29415:change ote location to fix auto-sync Sep 16, 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 Sep 16, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 16, 2025

@kuiwang02: This pull request references OCPQE-29415 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.21.0" version, but no target version was set.

Details

In response to this:

/cc @perdasilva @jianzhangbjz

I am sorry the auto-sync is broken after #1105 is merged.
Per https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-auto-olm-downstreaming/1967740380359168000, it treats tests-extension as repo if I put it under staging directory.

so, I change the tests-extension location to fix auto-sync.

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
Copy Markdown
Contributor Author

kuiwang02 commented Sep 16, 2025

/retitle OCPQE-29415:UPSTREAM:: change ote location to fix auto-sync

@openshift-ci openshift-ci Bot changed the title OCPQE-29415:change ote location to fix auto-sync OCPQE-29415:UPSTREAM:<carry>: change ote location to fix auto-sync Sep 16, 2025
@kuiwang02
Copy link
Copy Markdown
Contributor Author

/hold

I would like to revert #1105 to resolve the auto-sync issue.

@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 Sep 16, 2025
@perdasilva
Copy link
Copy Markdown
Contributor

@kuiwang02 could you please rebase? I managed to get your revert down =D

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 16, 2025
@kuiwang02
Copy link
Copy Markdown
Contributor Author

@kuiwang02 could you please rebase? I managed to get your revert down =D

@perdasilva yes. I will rebase it and take it submit OTE again. thanks

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 17, 2025
@kuiwang02
Copy link
Copy Markdown
Contributor Author

kuiwang02 commented Sep 17, 2025

/retitile OCPQE-29415:add OTE into olmv0 with new location

@kuiwang02
Copy link
Copy Markdown
Contributor Author

kuiwang02 commented Sep 17, 2025

/retitle OCPQE-29415:add OTE into olmv0 with new location

@openshift-ci openshift-ci Bot changed the title OCPQE-29415:UPSTREAM:<carry>: change ote location to fix auto-sync OCPQE-29415:add OTE into olmv0 with new location Sep 17, 2025
@kuiwang02
Copy link
Copy Markdown
Contributor Author

@perdasilva @jianzhangbjz
the different between #1105 and #1108 :
1, move the tests-extension out of staging.
2, change extended directory name to qe per comment of olmv1 PR
3, change bindata to pkg per comment of olmv1 PR.

could you please help merge it? thanks

@kuiwang02
Copy link
Copy Markdown
Contributor 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 Sep 17, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

/lgtm
/verified by @kuiwang02

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 17, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@jianzhangbjz: This PR has been marked as verified by @kuiwang02.

Details

In response to this:

/lgtm
/verified by @kuiwang02

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 lgtm Indicates that a PR is ready to be merged. label Sep 17, 2025
@jianzhangbjz
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 17, 2025

[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 Sep 17, 2025
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 30bd29b and 2 for PR HEAD 62ce21a in total

@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 17, 2025

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 56f9906 into openshift:main Sep 17, 2025
16 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants