failed to read client configuration template file: open /host/etc/beegfs/beegfs-client.conf: no such file or directory about beegfs-csi-driver

[gmarks-ntap]

Hi @titansmc,

The controller service has always had a requirement to be running on a node with the beegfs packages installed, at least for full functionality. There was some additional validation added in v1.2.1 to verify the existence of the beegfs utilities on the nodes running the driver and this validation is where you are now running in to the error. See 4207846 for the particular commit if you're interested.

Thinking about your situation, I'm wondering if you statically provision your volumes? The controller service only really needs to use the beegfs utilities when it dynamically provisions volumes. Before the extra validation was added, the controller service would likely never fail if it was never asked to dynamically create a volume so you may have been unknowingly working around that requirement. If you were using dynamic provisioning prior to v1.2.1 then I'm not currently sure how that was working and additional information might be helpful.

[titansmc]

Thanks for the explanation. That was the case, we manually provision an existing volume and make it available in k8s.
All good then!