-
Notifications
You must be signed in to change notification settings - Fork 30
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
Failed to create IBM Cloud VPC Block CSI Driver on Single Node OpenShift in IBM Cloud VPC #155
Comments
Thanks @aazraq for opening this issue. Adding few findings
Point of failure - https://github.com/IBM/ibm-csi-common/blob/master/pkg/metadata/metadata.go#L89-L97 Added labels manually to bring driver pods up
Pods came to healthy state. We see errors in PVC
|
node-pod was still in CrashLoopBackoff node-driver-registart is unable to connect to socket I did
It has some permission issues |
Suggest following up on this reported issue (now closed) which looks like the problem you are hitting: kubernetes-csi/node-driver-registrar#36 (comment) |
@jsafrane Could you please help here to check what permission is missing for selinux. |
This smells like SELinux. In RHEL, we traditionally run both CSI driver and driver registrar as privileged containers, so both can access the host ( Running the registrar as I don't know what prevents the registrar to access
You see anything else, who changed the contexts and why? |
@aazraq Could you share above command O/P from your setup. |
@jsafrane Another team reported similar issue where node-driver pods were restarting. I checked all commands which you mentioned in above comment.
Do you see any gap here @jsafrane |
Sorry, I was wrong. This is not true;
Only privileged containers can write to directory with label |
@jsafrane Is this specific to RHCOS environment.. because above deployment just works fine on Managed Clusters [IBM IKS and ROKS ] |
Also with
|
Thank you @jsafrane |
/close |
@jsafrane: Closing this issue. 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/test-infra repository. |
Environment details:
Single Node OpenShift cluster running on IBM Cloud VPC VSI.
OpenShift: 4.12
Problem Description:
I tried to follow the instructions here, and built the image from the master branch and pushed it to IBM Cloud Container Registry. However this command failed
bash deploy/kubernetes/driver/kubernetes/deploy-vpc-block-driver.sh stage
with this issue
I contacted @ambiknai who was very helpful and very generous with her time and troubleshooted the issue with me, and gave me manual yaml files which progressed the CSI driver creation, but still it's failing with the below issue.
Attached are the logs.
csi-provisioner.log
ibm-vpc-block-csi-controller.log
The text was updated successfully, but these errors were encountered: