STOR-2598: Rebase to upstream v2.1.11 for OCP 4.21#106
Conversation
…2.1.8 Post release PR for release v2.1.8
…clean Cherry pick PRs for release 2.1.9
…-2.1.9 Pre-release PR 2.1.9 release
….1.9 Post release PR 2.1.9
Change summary: 1) Address issue 1659: Invalid golang.org/x/net checksum and kubernetes version. go.sum was regenerated with `go mod tidy`, vendored dependencies where updated with `go mod vendor` 2) Upgrade k8s modules to 33.2, and clean go.mod replace directive 3) Update mock_k3s_client.go using update-gomock script output
…correct Release 2.1.10 cherry pick
…correct Pre-release PR 2.1.10 release
…1.10 Post release PR release 2.1.10
- Fix spelling errors in comments and logs: * 'retring' → 'retrying' in node.go * 'proccessing' → 'processing' in efs_watch_dog.go logs - Replace deprecated io/ioutil functions for Go 1.16+ compatibility: * ioutil.ReadDir() → os.ReadDir() in efs_watch_dog.go * ioutil.TempDir() → os.MkdirTemp() in tests * ioutil.WriteFile() → os.WriteFile() in tests * ioutil.ReadFile() → os.ReadFile() in reaper.go and tests All tests pass and functionality remains unchanged.
PR testing failed when reverting line to clean_install 3.0.8 openssl packages. Creating this commit to test with clean_install and unpinned openssl packages.
…l-2.1.11 Cherry pick rel 2.1.11
…-release Pre-release PR for 2.1.11 release
|
@dfajmon: This pull request references STOR-2598 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. DetailsIn 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. |
Additional changes: - remove .github files - do not overwrite GOARCH in makefile - go mod tidy && go mod vendor
4110057 to
5048fe3
Compare
|
@dfajmon: This pull request references STOR-2598 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. DetailsIn 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. |
|
@dfajmon: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@dfajmon: This pull request references STOR-2598 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. DetailsIn 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. |
|
This is rebase to 2.1.14! Please update the changelogs + link to diff to upstream |
|
Hi @jsafrane, the previously rebase is to |
|
@jsafrane branches cant be renamed after PR is open, it used to be v2.1.14 based after checking that the newest version has incompatible go version I switched to v2.1.11. Also mentioned in the Description in PR
|
|
I see. Still, please update the "Diff to upstream v2.1.11" link, it's dead |
|
@dfajmon: This pull request references STOR-2598 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. DetailsIn 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 |
|
/unassign @duanwei33 @chao007 @radeore |
|
@Phaow: This PR has been marked as verified by DetailsIn 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. |
146aab3
into
openshift:master
Issue link
https://issues.redhat.com/browse/STOR-2598
Diff to upstream v2.1.11
kubernetes-sigs/aws-efs-csi-driver@v2.1.11...dfajmon:rebase-v2.1.14
Notes for reviewers
Rebasing to v2.1.11 because newer versions use go 1.25+ which we don't support for OCP 4.21.
Changes Summary
Full changelog
https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-2.x.md
Last rebase
#97
@openshift/storage