-
Notifications
You must be signed in to change notification settings - Fork 134
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
Volume cannot be accessed when csi-smb-node-xxxxx pod on the same node as the node of the pod which is using PV is restarted. #130
Comments
related to #64 ? |
githubformichael
changed the title
Volume cannot be accessed when csi-smb-node-xxxxx pod on the same node as the pod which is using PV is restarted.
Volume cannot be accessed when csi-smb-node-xxxxx pod on the same node as the node of the pod which is using PV is restarted.
Oct 5, 2020
4 tasks
@githubformichael could you try the fix in PR: #131? thanks. |
okay. thanks! |
I have released https://github.com/kubernetes-csi/csi-driver-smb/releases/tag/v0.4.0, pls try that version, thanks. |
@andyzhangx , Thank you for your hard work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
SMB CSI volume becomes UN-Accessible when csi-smb-node is restarted.
What you expected to happen:
SMB CSI volume should still be accessible when csi-smb-node pods are restarted.
How to reproduce it:
Error message: "ls: /mnt/smb: Resource temporarily unavailable. command terminated with exit code 1"
or " Host is down"
Anything else we need to know?:
This is a critical issue, please fix it as soon as possible!
Environment:
CSI Driver version: v0.3.0
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"9f2892aab98fe339f3bd70e3c470144299398ace", GitTreeState:"clean", BuildDate:"2020-08-13T16:12:48Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
OS (e.g. from /etc/os-release):
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=2135.6.0
VERSION_ID=2135.6.0
BUILD_ID=2019-07-30-0722
PRETTY_NAME="Container Linux by CoreOS 2135.6.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Kernel (e.g.
uname -a
):Linux xxxxx 4.19.56-coreos-r1 test: fix travis config #1 SMP Tue Jul 30 06:40:10 -00 2019 x86_64 Intel(R) Xeon(R) CPU E3-1240 v3 @ 3.40GHz GenuineIntel GNU/Linux
Install tools:
Others:
The text was updated successfully, but these errors were encountered: