I fixed this by replacing the csi-cinder-controllerplugin and the csi-nodeplugin using the manifests found in this project: https://github.com/kubernetes/cloud-provider-openstack.

I used kubectl to make the changes. Does anyone know if end-users can configure these kinds of changes when kolla-ansible installs magnum? Or when creating the cluster template?

Thanks,
-Stu
From: Stuart Whitman
Sent: Thursday, October 20, 2022 10:09 AM
To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: [kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
 
Hello,

When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod:
E1020 13:38:41.747511       1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resource                                                                                                                                                                    
E1020 13:38:41.748187       1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resource
​I fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project.

I'm not finding any help with this error on Google.

Thanks,
-Stu 
_____________________________________
The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.