Skip to content
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

STOR-2007: Rebase to upstream v10.26.0 for OCP 4.18 #12

Merged
merged 21 commits into from
Oct 17, 2024

Conversation

gapra-msft and others added 19 commits June 17, 2024 16:55
* Release pipeline for linux, mariner, mac and windows

* Release pipeline for linux, mariner, mac and windows

* incorporated review comments

* incorporated review comments

* incorporated review comments

* incorporated review comments

* resolved conflicts

* testes

* tested

* incorporated review comments

* incorporated review comments

* incorporated review comments
* Add flag to release to container for private drop or GA release
* Migrated smoke tests for auto detect blob type
* Release pipeline for linux, mariner, mac and windows
* Release pipeline for linux, mariner, mac and windows
* Release pipeline for linux, mariner, mac and windows
* Release pipeline for linux, mariner, mac and windows
@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 3, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2024

@dfajmon: This pull request references STOR-2010 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.18.0" version, but no target version was set.

In response to this:

Issue link:
https://issues.redhat.com/browse/STOR-2010

Diff to upstream v10.26.0:
Azure/azure-storage-azcopy@v10.26.0...dfajmon:rebase-10.26.0

Changes between 10.25.1 (OCP 4.17) and 10.26.0 (OCP 4.18):

Full changelogs:
https://github.com/Azure/azure-storage-azcopy/releases/tag/v10.26.0

@openshift/storage

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 requested review from gnufied and tsmetana September 3, 2024 12:01
@dfajmon dfajmon changed the title STOR-2010: Rebase to upstream v10.26.0 for OCP 4.18 STOR-2007: Rebase to upstream v10.26.0 for OCP 4.18 Sep 3, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2024

@dfajmon: This pull request references STOR-2007 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.18.0" version, but no target version was set.

In response to this:

Issue link:
https://issues.redhat.com/browse/STOR-2010

Diff to upstream v10.26.0:
Azure/azure-storage-azcopy@v10.26.0...dfajmon:rebase-10.26.0

Changes between 10.25.1 (OCP 4.17) and 10.26.0 (OCP 4.18):

Full changelogs:
https://github.com/Azure/azure-storage-azcopy/releases/tag/v10.26.0

@openshift/storage

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.

@dfajmon
Copy link
Author

dfajmon commented Sep 5, 2024

/retest

1 similar comment
@dfajmon
Copy link
Author

dfajmon commented Sep 5, 2024

/retest

@dfajmon
Copy link
Author

dfajmon commented Sep 6, 2024

/retest

@jsafrane
Copy link

jsafrane commented Sep 12, 2024

@dfajmon can you please update .ci-operator.yaml and Dockerfile with today's main? It was updated to 4.18.

edit: ART will sync the files automatically

@jsafrane
Copy link

/lgtm
/approve
/label px-approved
/label docs-approved

@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Sep 16, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 16, 2024
Copy link

openshift-ci bot commented Sep 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfajmon, jsafrane

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 Sep 16, 2024
@dfajmon
Copy link
Author

dfajmon commented Oct 7, 2024

@ropatil010 can you check the status on this one please?

Additional changes:
- remove .github files
- remove .gitignore
- add .snyk file
- go mod tidy && go mod vendor
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2024
Copy link

openshift-ci bot commented Oct 17, 2024

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

@ropatil010
Copy link

Adding label based on the test results.

Profile: ipi-on-azure/versioned-installer-ci
Platform: Azure
Payload: 4.18.0-0.test-2024-09-26-145156-ci-ln-zzim4x2-latest

Azure disk driver version:
oc logs pod/azure-disk-csi-driver-controller-7c578d575-6rdmk -c csi-driver
{"name":"disk.csi.azure.com","vendor_version":"v1.30.4"}
Azure file driver version:
oc logs pod/azure-file-csi-driver-controller-85b549c788-jswp2 -c csi-driver
{"name":"file.csi.azure.com","vendor_version":"v1.30.5"}
Az copy version:
oc exec -it pod/azure-file-csi-driver-controller-85b549c788-jswp2 -n openshift-cluster-csi-drivers -c csi-driver /bin/bash
bash-5.1$ /bin/./azcopy --version
azcopy version 10.26.0
For Azure File driver:
quay.io/rhn_support_ropatil/azfile@sha256:1c7f0be9da9823f250e4e698899e66b275c6fe79a98545dd363d7c77c63c189f

https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/ginkgo-test/271329/console
10-01 19:01:18.049 109 pass, 159 skip (2h50m56s)

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 17, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 17, 2024

@dfajmon: This pull request references STOR-2007 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.18.0" version, but no target version was set.

In response to this:

Issue link:
https://issues.redhat.com/browse/STOR-2007

Diff to upstream v10.26.0:
Azure/azure-storage-azcopy@v10.26.0...dfajmon:rebase-10.26.0

Changes between 10.25.1 (OCP 4.17) and 10.26.0 (OCP 4.18):

Full changelogs:
https://github.com/Azure/azure-storage-azcopy/releases/tag/v10.26.0

@openshift/storage

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.

@mpatlasov
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 035211a into openshift:main Oct 17, 2024
6 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-azure-storage-azcopy-base
This PR has been included in build ose-azure-storage-azcopy-base-container-v4.18.0-202410171641.p0.g035211a.assembly.stream.el9.
All builds following this will include this PR.

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. docs-approved Signifies that Docs has signed off on this PR 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. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.