Moritz Wanzenböck

> The link https://gitlab.at.linbit.com/linstor/linstor-server is not working for me, did you mean https://github.com/LINBIT/linstor-server? Yes, sorry, used the internal link there...

The timeout is created by the CSI sidecars. In this case I think it's here: https://github.com/kubernetes-csi/external-attacher/ (`--timeout`) which seems to default to 15s. I thought it was 1m, but that...

Sure. For completeness, I added some flags to curl to make it work with mTLS (the debug output in the logs does not handle that correctly), and also my deployment...

I think that is only emitted when the ctx is cancelled. That probably happens somewhere in the grpc server, when the RPC call itself is canceled/times out

> When running linstor-satellite in a container, it depends on LVM configuration from a host Not true, at least for stuff managed by piraeus. We use a separate LVM config...

So the issue is because of the missing thin tools the thinpool LV is never activated, which means LINSTOR also can't use it? So a simple solution would be that...

Just hit this issue myself in my test environment :facepalm: @ghernadi opinion on adding activation commands when a satellite starts/a new storage pool is added?

One of the issues here in particular is that an inactive thinpool does not report the free percentage, which is actually what trips up LINSTOR I believe

Hi! This is definitely not normal. The system might take one or two minutes to start if there is a migration happening, but that is not the case here. Would...

Definitly possible. I think I remember seeing a bug where properties of snapshots would not get cleaned up, but I never reproduced it. If you run `grep /snapshots/ propscontainers.internal.linstor.linbit.com.yaml`, do...