Moritz Wanzenböck

> I mean, every k8-node must have the same disks No you, can have completely different disk and storage pools on every node > Can this storage work in k8-cluster...

First thing: I'm surprised it even lets you have a `ReadWriteMany` resource at all... Secondly: I'd prefer it if the user had to explicitly opt-in (maybe through a new `enable-live-migration`...

Have you checked the actual drbd resource (`drbdsetup show --show-defaults`)? Because whatever you set in the storage class is put on the resource group and inherited by the resource definition

> * nodePublishVolume: add check: > if volume has type: Block and accessMode: ReadWriteMany; > if it is already InUse at one other node; > then enable allow-two-primaries flag >...

It's complicated. The issue with linstor-gateway in this context is that it is basically a whole different project, which is mainly aimed at running directly on the host. So we...

Please share the reprocuder if you can, but I can't promise when I'll find the time to verify it. I had a look through the linked ticket. I'm not really...

Weird. Since the error seems to be in `listBackups` (which gets called by the CSI driver on creation) I assume it's not actually about any snapshot it tries to create,...

> ``` > I0819 16:05:29.747960 1 csi_handler.go:234] Error processing "csi-d9e810a254b0ffa73804d0480a395b9e575625dd0482256f9213db53b5fc908b": failed to attach: rpc error: code = Internal desc = ControllerPublishVolume failed for pvc-7e1063f2-b831-41a6-8c85-fee1fbf6c483: failed to check existing assignment: context...

> can you possibly link me to the controller code which does the check on the linstor side? That's the entry on the csi plugin side: https://github.com/piraeusdatastore/linstor-csi/blob/master/pkg/driver/driver.go#L613 And thats were...

Hmm, I'm not sure on the order of those log lines. It could be that there are multiple requests interleaved. We should probably start adding a request ID to the...