Skip to content

[oadp-1.4] OADP-4995: Add support for legacy aws plugin #1570

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 1 commit into from
Oct 24, 2024

Conversation

sseago
Copy link
Contributor

@sseago sseago commented Oct 23, 2024

Why the changes were made

Certain s3 providers don't support the AWS SDK v2 updates made in velero-plugin-for-aws v1.9+ (OADP 1.4+). This PR provides the ability to use the v1.8 plugin in a newer OADP environment.

How to test the changes made

In the DPA DefaultPlugins section, use legacy-aws instead of aws. S3 providers that work with the regular aws plugin should still work here. S3 providers that error out in various ways with the regular plugin should also work.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2024
@sseago sseago changed the title Add support for legacy aws plugin (#1565) OADP-4995 Add support for legacy aws plugin Oct 23, 2024
@sseago
Copy link
Contributor Author

sseago commented Oct 23, 2024

/override ci/prow/4.17-e2e-test-kubevirt-aws

Copy link

openshift-ci bot commented Oct 23, 2024

@sseago: Overrode contexts on behalf of sseago: ci/prow/4.17-e2e-test-kubevirt-aws

In response to this:

/override ci/prow/4.17-e2e-test-kubevirt-aws

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.

Copy link

openshift-ci bot commented Oct 23, 2024

@sseago: 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/4.18-dev-preview-e2e-test-aws 9c4e9a9 link false /test 4.18-dev-preview-e2e-test-aws
ci/prow/4.17-e2e-test-kubevirt-aws 9c4e9a9 link true /test 4.17-e2e-test-kubevirt-aws

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.

@mateusoliveira43 mateusoliveira43 changed the title OADP-4995 Add support for legacy aws plugin [oadp-1.4] OADP-4995: Add support for legacy aws plugin Oct 24, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 24, 2024

@sseago: This pull request references OADP-4995 which is a valid jira issue.

In response to this:

Why the changes were made

Certain s3 providers don't support the AWS SDK v2 updates made in velero-plugin-for-aws v1.9+ (OADP 1.4+). This PR provides the ability to use the v1.8 plugin in a newer OADP environment.

How to test the changes made

In the DPA DefaultPlugins section, use legacy-aws instead of aws. S3 providers that work with the regular aws plugin should still work here. S3 providers that error out in various ways with the regular plugin should also work.

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 Oct 24, 2024
@@ -153,7 +153,7 @@ metadata:
Cloud Provider,Developer Tools,Modernization & Migration,OpenShift Optional,Storage
certified: "false"
containerImage: quay.io/konveyor/oadp-operator:oadp-1.4
createdAt: "2024-05-29T17:22:16Z"

Choose a reason for hiding this comment

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

this change is right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mateusoliveira43 This file was created from make bundle -- I'm not sure why createdAt was removed. I just tried again in my checkout, removed the file and re-ran make bundle and it's the same.

@shubham-pampattiwar @kaovilai Any idea why this would happen?

@weshayutin
Copy link
Contributor

whayutin@thinkdoe:/tmp$ oc get dpa dpa-sample -o yaml | grep aws
      provider: aws
      - aws
      provider: aws
whayutin@thinkdoe:/tmp$ oc get dpa dpa-sample -o yaml | grep aws
      provider: aws
      - legacy-aws
      provider: aws
whayutin@thinkdoe:/tmp$ oc get dpa dpa-sample -o yaml | grep -i recon
    message: Reconcile complete
    type: Reconciled

also ran a backup w/ legacy-aws

vol24-ttl-short   Completed   0        0          2024-10-24 13:59:10 +0000 UTC   55m       dpa-sample-1       <none>l

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.

/LGTM

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

openshift-ci bot commented Oct 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, sseago, 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 11ab518 into openshift:oadp-1.4 Oct 24, 2024
21 of 22 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.

5 participants