-
Notifications
You must be signed in to change notification settings - Fork 13
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
OCPBUGS-43823: Downgrade to upstream v1.29.11 for OCP 4.18 #88
OCPBUGS-43823: Downgrade to upstream v1.29.11 for OCP 4.18 #88
Conversation
…ot/cherry-pick-2389-to-release-1.29 [release-1.29] test: fix trivy action failure
…iskSlotNum-charts [release-1.29] feat: add ReservedDataDiskSlotNum to helm-chart
…m-x55m-1.29 [release-1.29] fix: GHSA-xr7q-jx4m-x55m
[release-1.29] feat: add tagValueDelimiter parameter
…1.29 [release-1.29] fix: CVE-2024-5321
…ry-limits-1.29 [release-1.29] fix: increase azuredisk container memory limits as 600Mi
fix fix fix
…ot/cherry-pick-2429-to-release-1.29 [release-1.29] feat: support NVME disk
…permission-1.29 [release-1.29] fix: add pv patch permission with HonorPVReclaimPolicy enabled
doc: cut v1.29.8 release
…edgezone-1.29-2 [release-1.29] fix: create snapshot failure in edge zone
fix fix fix fix
…-e2e-test-1.29 [release-1.29] test: use workload identity for e2e test
…ot/cherry-pick-2461-to-release-1.29 [release-1.29] fix: checkDiskLun throttling issue
…sioner-5.0.2-1.29 [release-1.30] fix: upgrade csi-provisioner to v5.0.2 to fix pv deletion stuck issue
doc: cut v1.29.9 release
…ot/cherry-pick-2611-to-release-1.29 [release-1.29] chore: update max data disk num
…elimiter-1.29 [release-1.29] fix: tagValueDelimiter parameter mismatch
…ot/cherry-pick-2630-to-release-1.29 [release-1.29] cleanup: refine logging
doc: cut v1.29.11 release
remove .github go mod vendor && go mod tidy
@dfajmon: This pull request references Jira Issue OCPBUGS-43823, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. 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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dfajmon, dobsonj 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 |
/retest |
dcf4766
into
openshift:master
@dfajmon: Jira Issue OCPBUGS-43823: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-43823 has been moved to the MODIFIED state. 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. |
[ART PR BUILD NOTIFIER] Distgit: ose-azure-disk-csi-driver |
Downgrade to v1.29.11. This bug is produced by v1.30.0, where the stack2 SDK is implemented. See the issue. Unfortunately, we can't use the newest release because it's go 1.23, and OCP 4.18 is go 1.22.
I wanted to cherry-pick the fix, but there are big jumps with the dependencies and versions,
e.g., azclient v0.0.31->v0.1.18 (which also produces go1.23 dependency)
So we decided to downgrade to 1.29.11 instead. OCP 4.19 will have release 1.3X.X.
Issue link:
https://issues.redhat.com/browse/OCPBUGS-43823
Diff to upstream v1.29.9:
kubernetes-sigs/azuredisk-csi-driver@v1.29.9...dfajmon:rebase-v1.29.11
Changes between v1.29.9 (OCP 4.17) and v1.29.11 (OCP 4.18):
Full changelogs:
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.29.11
https://github.com/kubernetes-sigs/azuredisk-csi-driver/releases/tag/v1.29.10
@openshift/storage