[DRBD-user] No quorum on UpToDate devices

[kvaps]

Hi, any idea why drbd can lose their quorum? All the replicas are UpToDate:

root at kube-node-14:/# drbdsetup status
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Primary
  disk:Diskless
  kube-node-4 role:Secondary
    peer-disk:UpToDate
  kube-node-6 role:Secondary
    peer-disk:UpToDate

root at kube-node-6:/# drbdsetup status
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Secondary suspended:quorum
  disk:UpToDate quorum:no blocked:upper
  kube-node-14 role:Primary
    peer-disk:Diskless
  kube-node-4 role:Secondary
    peer-disk:UpToDate

root at kube-node-4:/# drbdsetup status
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d
pvc-2ba7ccd7-e92c-4c92-be8e-6e55c9a0840d role:Secondary suspended:quorum
  disk:UpToDate quorum:no blocked:upper
  kube-node-14 role:Primary
    peer-disk:Diskless
  kube-node-6 role:Secondary
    peer-disk:UpToDate


Best Regards,
Andrei Kvapil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20230315/a72f3ef0/attachment.htm>