Moritz Wanzenböck

Since working on Operator 2.0 I'm also back thinking about this issue. Specifically these points: > Possible problem, that if user would install drbd-utils some time on the node, it...

> Some legacy systems already have drbd installed on the host with drbdadm That may complicate things again, since if you installed drbdadm on the host, you probably already have...

What do you get when running ``` kubectl exec deployment/piraeus-op-cs-controller -- linstor v l ``` Do you see volumes without a device path? I think there was a bug in...

Please try using `quay.io/pireausdatastore/piraeus-server:v1.15.0` if you have not already (set it for operator.controller.controllerImage and operator.satelliteSet.satelliteImage). This looks exactly like an issue thats already solved in 1.15.0

That is very strange, especially that it resolves after a restart. Do you still have the machines and could you share the kernel logs?

I would prefer to use an approach similar to container resources: https://github.com/piraeusdatastore/piraeus-operator/blob/master/examples/resource-requirements.yaml I.e. we provide another example config file: ```yaml csi-snapshotter: image: private.example.com/piraeus/snapshot-controller:v2.1.0 csi: pluginImage: private.example.com/piraeus/piraeus-csi:v0.9.0 csiAttacherImage: private.example.com/piraeus/csi-attacher:v2.2.0 ... ```...

Sure. It would be good to discuss something concrete :+1:

Thank you for reporting this issue. You are right in your suspicion that symlinks don't work. If a storage pool does not exist on a node, it will try to:...

Yeah, you can leave it open.

Hello! You don't need a storage pool, but at least a satellite running on the host. This can be directly on the host or as a daemonset (like [the one...