-
Notifications
You must be signed in to change notification settings - Fork 173
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
csi-controller v2.0.0-rc.1 does not start when no vSAN file service is enabled #193
Comments
hello!! kubectl describe pod vsphere-csi-node-wbnn4 -n=kube-system Normal Scheduled 29m default-scheduler Successfully assigned kube-system/vsphere-csi-controller-76b8d7d97b-gz4j9 to seliicbl01526-k8sw kubectl get pods -A -o wide curl http://10.1.248.1:9808 ping 10.1.248.1 |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
vsphere csi controller deployment does not start when the controller does not succeed to find file service backed by vSAN. In an environment where vSAN is not present, the
getDsToFileServiceEnabled
function fails, and the controller does not successfully start.This happens when
TargetvSANFileShareDatastoreURLs
is not configured.What you expected to happen:
Expected the controller to successfully start, and to be able to provide the devices through the storage class.
How to reproduce it (as minimally and precisely as possible):
In an environment without vSAN or file services (vSphere 6.7u3) the controller does not start.
Anything else we need to know?:
760b9ab looks to have introduced this bug, where previous errors would be ignored.
Environment:
uname -a
): 4.18.0-147.5.1.el8_1.x86_64The text was updated successfully, but these errors were encountered: