Skip to content

[oadp-1.5] OADP-5782: Add hypershift-oadp-plugin as a default one in oadp-operator + E2E #1729

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 24, 2025

Conversation

jparrill
Copy link
Contributor

Why the changes were made

Manual backport of:

How to test the changes made

Details on the original PR

@jparrill jparrill changed the title Bp oadp1.5/hcp e2e [oadp-1.5] OADP-5782: Add hypershift-oadp-plugin as a default one in oadp-operator + E2E Apr 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 24, 2025

@jparrill: This pull request references OADP-5782 which is a valid jira issue.

In response to this:

Why the changes were made

Manual backport of:

How to test the changes made

Details on the original PR

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 24, 2025
@openshift-ci openshift-ci bot requested review from hhpatel14 and sseago April 24, 2025 08:16
@jparrill
Copy link
Contributor Author

jparrill commented Apr 24, 2025

/jira cherrypick OADP-5782

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 24, 2025

@jparrill: Ignoring requests to cherry-pick non-bug issues: OADP-5782

In response to this:

/jira cherrypick OADP-5782

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.

Signed-off-by: Juan Manuel Parrilla Madrid <[email protected]>
@jparrill jparrill force-pushed the bp-oadp1.5/hcp-e2e branch from 8786e58 to 2299afe Compare April 24, 2025 08:34
@jparrill
Copy link
Contributor Author

jparrill commented Apr 24, 2025

/test 4.19-e2e-test-hcp-aws

Infra failure...

@jparrill
Copy link
Contributor Author

/test 4.19-e2e-test-kubevirt-aws

@jparrill
Copy link
Contributor Author

/retest

@weshayutin
Copy link
Contributor

/test 4.19-e2e-test-aws

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 24, 2025
@kaovilai
Copy link
Member

/lgtm

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

openshift-ci bot commented Apr 24, 2025

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

Copy link
Contributor

@weshayutin weshayutin left a comment

Choose a reason for hiding this comment

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

/approved /lgtm

Copy link

openshift-ci bot commented Apr 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill, kaovilai, weshayutin

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-merge-bot openshift-merge-bot bot merged commit 485d3ce into openshift:oadp-1.5 Apr 24, 2025
9 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants