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

OCPBUGS-33039: Rebase v1.29.5 for OCP 4.14 #66

Merged

Conversation

andyzhangx and others added 30 commits July 13, 2023 08:47
…ecret-print

cleanup: remove secret print in error message
…ubeconfig-setting

fix: use InClusterConfig by default on Windows node
…ot/go_modules/google.golang.org/protobuf-1.31.0

build(deps): bump google.golang.org/protobuf from 1.28.1 to 1.31.0
Bumps [k8s.io/pod-security-admission](https://github.com/kubernetes/pod-security-admission) from 0.27.1 to 0.27.3.
- [Commits](kubernetes/pod-security-admission@v0.27.1...v0.27.3)

---
updated-dependencies:
- dependency-name: k8s.io/pod-security-admission
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…ot/go_modules/k8s.io/pod-security-admission-0.27.3

build(deps): bump k8s.io/pod-security-admission from 0.27.1 to 0.27.3
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.10.0 to 0.12.0.
- [Commits](golang/net@v0.10.0...v0.12.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…ot/go_modules/golang.org/x/net-0.12.0

build(deps): bump golang.org/x/net from 0.10.0 to 0.12.0
Bumps [k8s.io/api](https://github.com/kubernetes/api) from 0.27.3 to 0.27.4.
- [Commits](kubernetes/api@v0.27.3...v0.27.4)

---
updated-dependencies:
- dependency-name: k8s.io/api
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…ot/go_modules/k8s.io/api-0.27.4

build(deps): bump k8s.io/api from 0.27.3 to 0.27.4
Bumps [k8s.io/pod-security-admission](https://github.com/kubernetes/pod-security-admission) from 0.27.3 to 0.27.4.
- [Commits](kubernetes/pod-security-admission@v0.27.3...v0.27.4)

---
updated-dependencies:
- dependency-name: k8s.io/pod-security-admission
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…eprecated-versions3

cleanup: update new chart versions and remove deprecated versions
…ot/go_modules/k8s.io/pod-security-admission-0.27.4

build(deps): bump k8s.io/pod-security-admission from 0.27.3 to 0.27.4
…eprecated-versions4

cleanup: update new chart versions and remove deprecated versions
…leShareFailureCache

fix: stop resize file share when account limit is exceeded
…unt-cache

fix: add StorageAccountCache to avoid querying storage account frequently
…-dependabot-limit

chore: increase dependabot PR limit
Bumps [github.com/container-storage-interface/spec](https://github.com/container-storage-interface/spec) from 1.7.0 to 1.8.0.
- [Release notes](https://github.com/container-storage-interface/spec/releases)
- [Commits](container-storage-interface/spec@v1.7.0...v1.8.0)

---
updated-dependencies:
- dependency-name: github.com/container-storage-interface/spec
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@RomanBednar
Copy link
Author

/override ci/prow/verify-commits

Copy link

openshift-ci bot commented Apr 26, 2024

@RomanBednar: Overrode contexts on behalf of RomanBednar: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits

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/test-infra repository.

Copy link

openshift-ci bot commented Apr 26, 2024

@RomanBednar: The following test 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/verify-commits fe6e8ae link true /test verify-commits

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/test-infra repository. I understand the commands that are listed here.

@jsafrane
Copy link

/lgtm

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

/label cherry-pick-approved

Copy link

openshift-ci bot commented Apr 29, 2024

@jsafrane: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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/test-infra repository.

@duanwei33
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Apr 30, 2024
@duanwei33
Copy link

pre-merge verified with this open PR and openshift/azure-file-csi-driver-operator#104:

build 4.14.0-0.ci,#66,openshift/azure-file-csi-driver-operator#104

Followed https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/workload-identity-static-pv-mount.md to test static provision with PV, the pod with azure file volume gets running:

$ oc get pod -o wide
NAME                      READY   STATUS    RESTARTS   AGE     IP           NODE                                    NOMINATED NODE   READINESS GATES
statefulset-azurefile-0   1/1     Running   0          2m16s   10.130.2.6   wduan-e414-s2lvp-worker-eastus2-xxxvc   <none>           <none>

$ oc rsh statefulset-azurefile-0 
$ df -h | grep azure
//wduantestshare.file.core.windows.net/wduantest  100T  192K  100T   1% /mnt/azurefile
$ touch /mnt/azurefile/0507
$ ls /mnt/azurefile
0507  outfile  test

$ oc get pv pv-azurefile -o yaml | yq .spec.csi
driver: file.csi.azure.com
$ oc get pv pv-azurefile -o yaml | yq .spec.csi
driver: file.csi.azure.com
volumeAttributes:
  clientID: 1046015d-5b40-44ec-b7a9-448b31dedc15
  resourcegroup: wduan-share
  shareName: wduantest
  storageaccount: wduantestshare
volumeHandle: wduantestshare-wduantest

In the log we see the service account token is used to get the account key during NodePublishVolume:

I0507 01:07:54.249153       1 utils.go:77] GRPC call: /csi.v1.Node/NodeStageVolume
I0507 01:07:54.249175       1 utils.go:78] GRPC request: {"staging_target_path":"/var/lib/kubelet/plugins/kubernetes.io/csi/file.csi.azure.com/b1f27dbe8d29793b2f84c2e68a46e4479d99c7241549802a00f8902b5239c22b/globalmount","volume_capability":{"AccessType":{"Mount":{"mount_flags":["dir_mode=0777","file_mode=0777","uid=0","gid=0","mfsymlinks","cache=strict","nosharesock"],"volume_mount_group":"1000640000"}},"access_mode":{"mode":5}},"volume_context":{"clientID":"1046015d-5b40-44ec-b7a9-448b31dedc15","resourcegroup":"wduan-share","shareName":"wduantest","storageaccount":"wduantestshare"},"volume_id":"wduantestshare-wduantest"}
I0507 01:07:54.249463       1 nodeserver.go:173] Skip NodeStageVolume for volume(wduantestshare-wduantest) since clientID 1046015d-5b40-44ec-b7a9-448b31dedc15 is provided but service account token is empty


......
I0507 01:07:54.275187       1 utils.go:77] GRPC call: /csi.v1.Node/NodePublishVolume
I0507 01:07:54.275669       1 azurefile.go:799] clientID(1046015d-5b40-44ec-b7a9-448b31dedc15) is specified, use service account token to get account key

@duanwei33
Copy link

/label qe-approved
/label cherry-pick-approved

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

@RomanBednar: This pull request references Jira Issue OCPBUGS-33039, which is invalid:

  • expected dependent Jira Issue OCPBUGS-33038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Diff to upstream v1.29.5:
kubernetes-sigs/azurefile-csi-driver@v1.29.5...RomanBednar:azure-file-csi-driver:rebase-v1.29.5-ocp4.14

Notable changes:

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

@RomanBednar
Copy link
Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 7, 2024
@dobsonj
Copy link
Member

dobsonj commented May 8, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 8, 2024
@openshift-ci-robot
Copy link

@dobsonj: This pull request references Jira Issue OCPBUGS-33039, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-33038 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-33038 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

In response to this:

/jira refresh

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-merge-bot openshift-merge-bot bot merged commit f28a507 into openshift:release-4.14 May 8, 2024
9 checks passed
@openshift-ci-robot
Copy link

@RomanBednar: Jira Issue OCPBUGS-33039: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-33039 has been moved to the MODIFIED state.

In response to this:

Diff to upstream v1.29.5:
kubernetes-sigs/azurefile-csi-driver@v1.29.5...RomanBednar:azure-file-csi-driver:rebase-v1.29.5-ocp4.14

Notable changes:

@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-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-azure-file-csi-driver-container-v4.14.0-202405082212.p0.gf28a507.assembly.stream.el8 for distgit azure-file-csi-driver.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2024-05-08-232852

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet