Andrei Kvapil

And now I can't remove failed replica from linstor: ```bash # linstor r l -r pvc-f9db6a75-cdd1-4eec-8528-6bd68cb7e281 ╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ ┊ ResourceName ┊ Node ┊ Port ┊ Usage ┊ Conns ┊ State ┊...

I was trying to write config for `slt-dev-kube-worker-01` manually and recreating lvm volume with same size, then: ``` drbdadm create-md pvc-f9db6a75-cdd1-4eec-8528-6bd68cb7e281 drbdadm up pvc-f9db6a75-cdd1-4eec-8528-6bd68cb7e281 ``` resource become `Online` but it...

Ok after all, I solved this by removing resources and volumes maually from database and recreating PVC, then copying all the data to it.

@raltnoeder I know that. I'm just saying, that after few time it was removed but satellite does not monitored that situation until restart.

Just faced with this problem again, resource may stuck on DELETING if run this during RESIZING. Or opposite side, I'm not understood it well. **UPD1:** Resource continue stuck even after...

I meant that I was able to create a failed resource in Linstor, but there is no possibility to remove it Even after I loaded `nvmet` and `nvmet-rdma`, and passthrough...

Today we faced with this problem again, many resources were blocked by fact that they were trying to reach the node which was marked as `OFFLINE`: ``` ╭────────────────────────────────────────────────────────╮ ┊ Node...

If I try to restart just satellite, I see that linstor-controller not even try to reconnect it: [linstor-satellite3.log](https://github.com/LINBIT/linstor-server/files/5536016/linstor-satellite3.log)

Ah my bad, it seems last two cases we really have some connectivity issues with the node

Today was exactly same situation, the node had lack of RAM, after the reboot the controller didn't try to reconnect the node until restart ``` ╭───────────────────────────────────────────────────────╮ ┊ Node ┊ NodeType...