STOR-1591: Rebase to upstream v1.6.16 for OCP 4.17#39
Conversation
…-pick-of-#746-upstream-release-1.6 Automated cherry pick of kubernetes-sigs#746: Fix issue where errors were reported as info
…-pick-of-#737-kubernetes-sigs#770-kubernetes-sigs#774-upstream-release-1.6 Automated cherry pick of kubernetes-sigs#737: Add NfsExportOptions parsing#770: Refactor duplicate function#774: Disable NFSExportOptions by default
…t/cherry-pick-798-to-release-1.6 [release-1.6] Change base image from bullseye to bookworm for CVE fixes
…t/cherry-pick-836-to-release-1.6 [release-1.6] fix CVE-2024-28085
…t/cherry-pick-842-to-release-1.6 [release-1.6] Add dannawang0221 to OWNERS
…t/cherry-pick-848-to-release-1.6 [release-1.6] Update debian base image to fix CVE-2024-2961
…t/cherry-pick-873-to-release-1.6 [release-1.6] fix tier capacity check for expandVolume
… fix GO-2024-2746
…k-of-#864-upstream-release-1.6 Automated cherry pick of kubernetes-sigs#864: Properly unwrap gce-compute error code.
Manual cherrypick of kubernetes-sigs#878: Update k8s.io/kubernetes to fix GO-2024-2746
|
@dfajmon: This pull request references STOR-1593 which is a valid jira issue. 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. |
openshift-ci-robot
added
the
jira/valid-reference
dfajmon
changed the title
|
@dfajmon: This pull request references STOR-1591 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.17.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. |
|
/jira refresh |
|
@dfajmon: This pull request references STOR-1591 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.17.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
force-pushed
the
rebase-1.6.16
branch
4 times, most recently
from
fc1f58d to
e0d0de6
Compare
Reported to USPTREAM: kubernetes-sigs#896 Can be dropped if upstream adds this replace to go.mod: k8s.io/endpointslice => k8s.io/endpointslice v0.29.4 k8s.io/dynamic-resource-allocation => k8s.io/dynamic-resource-allocation v0.29.4 Commit fixes verify-deps check which was failing with: go: k8s.io/dynamic-resource-allocation@v0.0.0: invalid version: unknown revision v0.0.0 go: k8s.io/endpointslice@v0.0.0: invalid version: unknown revision v0.0.0 go: google.golang.org/genproto/googleapis/rpc@v0.0.0-20230822172742-b8732ec3820d: missing go.sum entry for go.mod file; to add it: go mod download google.golang.org/genproto/googleapis/rpc ERROR: go list -mod=readonly -m all failed with the message listed above. Cachito used in ART builds will fail to resolve dependencies offline. Typically, a pinned version is missing in go.mod, e.g.: replace k8s.io/foo => k8s.io/foo v0.26.0
|
@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. |
|
The failing |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dfajmon, RomanBednar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/label px-approved |
openshift-ci
Bot
added
px-approved
|
/assign @duanwei33 For QE approval |
|
@chao007 Hi, please see if we need some pre-merge checks for customer-visible features, thanks! |
|
@dfajmon @RomanBednar
|
|
@dfajmon It should be: |
|
@dfajmon: This pull request references STOR-1591 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.17.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. |
|
@duanwei33 fixed |
|
/lgtm |
|
/label qe-approved |
openshift-ci
Bot
added
the
qe-approved
|
@dfajmon: This pull request references STOR-1591 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.17.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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-gcp-filestore-csi-driver-container-v4.17.0-202407110611.p0.gb6ccd6a.assembly.stream.el9 for distgit ose-gcp-filestore-csi-driver. |
15 participants
Diff to upstream v1.6.16:
kubernetes-sigs/gcp-filestore-csi-driver@v1.6.16...dfajmon:rebase-1.6.16
Changes between v1.6.11 (OCP 4.16) and 1.6.16 (OCP 4.17):
Full changelogs:
https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/releases/tag/v1.6.16
@openshift/storage