Query regarding auto-promotion of secondary if primary linstor volume is not reachable

[saarthak18]

I have 4 node cluster and have 3 linstor volumes

currently as you can see node2 is the primary node

we were testing a scenario where the other node i.e is node 3 should be promoted to primary when node 2 is reboot (recreating the scenario where node2 is unreachable)

i have set this property in the storage class

storageClasses:
  - name: piraeus-storage
    provisioner: linstor.csi.linbit.com
    allowVolumeExpansion: true
    volumeBindingMode: WaitForFirstConsumer
    parameters:
      linstor.csi.linbit.com/storagePool: pool1
      linstor.csi.linbit.com/placementCount: "2"
      **property.linstor.csi.linbit.com/DrbdOptions/Resource/auto-promote: "yes"**

but still when i reboot the node2 which is primary it waits for it to become reachable and then make it primary

is there any other property that should be set?

[WanzenBug]

No, you don't need to set that property, it's the default. Most likely it is Kubernetes that is still holding a VolumeAttachment resource on the node to be rebooted. You can check that by kubectl describe pod <pod-name> on the Pod that should replace the one on node2. You will likely get a message that "PV is still attached to other node" or similar.

We have the HA Controller that should assist in these cases, you can check the logs of the ha-controller pods to see if they are working as expected.