Moritz Wanzenböck

Whatever solution we come up with, I don't think it will involve automatically wiping the database. This would be extremly painful for cases where the "LinstorCluster" resource was accidentally removed,...

Have you checked for firewall settings on both nodes? Looks like the k8s node is struggling to receive anything from the proxmox node.

> I did iperf3 tests from both nodes when on the same vlan on port 7000 and I'm getting >10 gbits per second and jitter below .02ms. No lost packets....

Sorry for the late response. > If a Linstor controller has more than one replica, only one target will be up in Prometheus. This is because of the leader election...

Since we now have the per-node `LinstorSatellite` resource, we could probably somehow "discover" what devices are available on a node beforehand. Currently the issue is that the API used by...

Yes, something like that. We need a way to reliably determine the available devices, and perhaps also a way to extend for example the LVM VG with new devices, as...

> Do you know how Linstor operators usually go about adding or removing disk from nodes Typically, they run some other provisioning solution (i.e. ansible, terraform, etc...) which maintains the...

Something has kept the resource open on `eu-central-1771`, as you can see in the `linstor volume list`. This is not allowed by DRBD, as only one node can access the...

That `kubectl exec eu-central-1771 -- drbdadm secondary pvc-22af8af6-3ecb-4216-b4d3-f1b5410266c9` suceeded would suggest that something or someone ran `drbdadm primary pvc-22af8af6-3ecb-4216-b4d3-f1b5410266c9`, which disables automatic demotion on removing the last writer. So I...

You might want to check older logs (`kern.log.1`, `kern.log.2`, etc..) to find the original `role( Secondary -> Primary )` message.