-
Notifications
You must be signed in to change notification settings - Fork 15
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
[BUG]: PowerFlex driver fails to start on RKE #1086
Comments
link: 19702 |
I am still having this issue. No problems till I used v2.7.0 version., however issue crops up when I used 2.9.1 and 2.9.2 NOTE: I have no problems when I deploy the CSI with 2.7.0. It works flawlessly!
I am seeing in the thread a particular ENV variable setting X_CSI_POWERFLEX_KUBE_NODE_NAME has been done as a fix. I am not sure, where is this value to be supplied as an end user. I do not see this setting anywhere in the values template documentation https://dell.github.io/csm-docs/docs/csidriver/installation/helm/powerflex/ Kindly suggest what should be done. |
Also adding the kubectl get nodes output |
Hi @thecloudgarage , According to the CSM 1.10 milestone associated with this issue, the resolution will be implemented in the v2.10.0 driver and subsequent releases of the csi-powerflex driver. Appreciate your comprehensive insights. Regards, |
I am running into this as well. Also had no issue with 2.7.0, wondering if there are workaround for making this work as 2.7.0 doesnt seem like an option within https://github.com/dell/csm-operator/tree/v1.5.0/samples |
Hi, there's no workaround that would work here, please switch to v2.10.0 driver. Thanks |
Bug Description
When PowerFlex driver is deployed on an environment having different hostname and kubernetes node names,
registrar
sidecar in the driver node pod is crashing with errorUnable to fetch the node labels. Error: nodes \"ip-10-x-x-x.ec2.internal\" not found"
and eventually ends up with error401 Unauthorized
after multiple restarts.Logs
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Deploy PowerFlex v2.8.0 driver with an environment having different hostnames and kubernetes node names.
Expected Behavior
Driver node pod should be in Running state.
CSM Driver(s)
CSI Driver for PowerFlex v2.8.0
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
RKE
Operating System
RHEL
The text was updated successfully, but these errors were encountered: