-
Notifications
You must be signed in to change notification settings - Fork 132
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
Object sync between container mount path on windows node and smb shared path doesn't happen even if volume mount succeeded #656
Comments
Hi Anyone faced this issue ? Can we have a root cause for this. |
I am also facing a similar issue with CSI SMB driver version v1.11.0 on K8s v1.27.x, with Windows node OS version server core 2019. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle stale |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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 kubernetes-sigs/prow repository. |
What happened:
We are using the csi smb on windows node on an onprem kubernetes for storage class and we are mounting pvc to windows container pod. We could see that PV and PVC are in bound state and pod is up and running but still we could see that the sync between the container mount path and smb shared path is missing.
There are 1800 objects on smb share path but on the container mount path there is no objects.
We checked the smb controller logs we could see below error:
2023-08-16T14:23:25.178452100+02:00 E0816 14:23:25.177792 23260 utils.go:81] GRPC error: rpc error: code = Internal desc = Could not mount target "c:\var\lib\kubelet\pods\7a4a66d4-ff25-49d6-99a9-173ca7ad63bd\volumes\kubernetes.io
csi\pvc-fa96da59-bde4-4d8b-82bf-42000ea6eb26\mount": open c:\var\lib\kubelet\pods\7a4a66d4-ff25-49d6-99a9-173ca7ad63bd\volumes\kubernetes.iocsi\pvc-fa96da59-bde4-4d8b-82bf-42000ea6eb26\mount: Access is denied.2023-08-16T14:24:07.158684000+02:00 E0816 14:24:07.158684 23260 utils.go:81] GRPC error: rpc error: code = NotFound desc = path c:\var\lib\kubelet\pods\7a4a66d4-ff25-49d6-99a9-173ca7ad63bd\volumes\kubernetes.io~csi\pvc-fa96da59-bde4-4d8b-82bf-42000ea6eb26\mount does not exist
Also we could confirm that when we restarted the pod the object sync works well and everything went fine again!
What you expected to happen:
When PVC is mounted successfully, all the objects from shared path and the container mount path should be in sync
How to reproduce it:
Anything else we need to know?:
Environment:
kubectl version
): 1.26.0+rke2r2uname -a
):Linux EDGEMASTER 5.10.0-23-amd64 test: fix travis config #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: