-
Notifications
You must be signed in to change notification settings - Fork 62
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
CSIProxy isn't igniting SMBGlobalMapping command #206
Comments
From the logs I'm not sure if this is the part where it hangs because that's the last statement that's printed in the method, there's actually additional code that runs and we don't have any confirmation about the other parts running or not. To narrow down the issue I'd add a |
I did some progress and fix the problem. It was a block on my Active Directory account. However, now I'm receiving the following:
Appears to be encapsulation the SMB-GlobalMapping command wrong. What should the exactly kubectl create secret command for a domain join? This is what I'm running:
Also tried:
|
Ok, it worked. This is the error: Windows System Error 87 |
@mauriciopoppe so the issue solved after worker node joined the domain? seems that's a manual step. |
At first I just joined the worker node in the domain due to the Windows System Error 87 and it worked, however my next Worker node which is Workgroup worked as well. Today I’ll investigate two things: 2 - It worked when using the latest 1.6.0 CSI-Driver. |
78c0fb7 Merge pull request kubernetes-csi#208 from jsafrane/skip-selinux 36e433e Skip SELinux tests in CI by default 348d4a9 Merge pull request kubernetes-csi#207 from RaunakShah/reviewers 1efc272 Merge pull request kubernetes-csi#206 from RaunakShah/update-prow 7d410d8 Changes to csi prow to run e2e tests in sidecars cfa5a75 Merge pull request kubernetes-csi#203 from humblec/test-vendor 4edd1d8 Add RaunakShah to CSI reviewers group 7ccc959 release tools update to 1.19 git-subtree-dir: release-tools git-subtree-split: 78c0fb714fa4448b29962a0f34fa18b7b7d97ae6
What happened:
CSIProxy isn't igniting SMBGLobalMapping command
As the mount isn't happening on the host, it throws a timeout; this sounds to be the root cause. CSIProxy isn't igniting the command. However, I can successfully run the SMB-GlobalMapping command manually.
Also, CSIProxy isn't detecting if an existing SMBGlobalMapping is already mounted. I did the test having the SMBGlobalMapping manually mounted.
CSIProxy Log:
kubelet log:
What you expected to happen:
CSIProxy to ignite SMBGlobalMapping command
How to reproduce it:
Using CSI-SMB-Driver.
Anything else we need to know?:
Environment:
kubectl version
): 1.22uname -a
): 10.0.17763 N/A Build 17763The text was updated successfully, but these errors were encountered: