Moritz Wanzenböck

See https://github.com/piraeusdatastore/piraeus-operator/issues/426#issuecomment-1465934727 for a workaround, and the overall issue

Can you verify that the `linstor-client-tls` secret is in use by the `linstor-wait-node-online` container? It should be set via environment variables.

It does have a purpose, namely to improve DRBD handling during shut down: By default, DRBD volumes created by Piraeus will suspend IO if connection is lost. During node shutdown,...

Since this is a mishmash of different issues. I'm going ahead and close this. If you just need a pointer on how to set up LINSTOR with an external cluster,...

Looks like LINSTOR does not implement the necessary logic for reading the snapshot data and sending to to S3. You could open an issue on the linstor-server project to see...

The docs could be a bit clearer, but snapshots in FILE_THIN storage pools only work when backed by XFS, not ext4. I'm guessing you are running ext4 as backing filesystem....

Flatcar is a tricky distribution to work with, and also one we do not have much experience with. We'd be happy to accept improvements by users.

Looks to be related to storage pool mixing: https://github.com/LINBIT/linstor-server/commit/700cb6281e2dec7f24f446780fe7ba2b5179524d So do you have a different type of storage pool on the new node?

No, for the user land tools (`drbdadm`, `drbdsetup`, etc...) it is all the same. Again, it may be some (uninteded) difference between node configurations. Could you share the output of...

That is probably why LINSTOR thinks it must involve the storage pool mixing. I'll do a bit of digging on when this property is added.