You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two halves of the same UpToDate-without-human-intervention story:
1. Dispatcher tags one diskful replica per RD (lex-lowest node name)
with drbd_options[auto-primary]=true. On firstActivation the
satellite Reconciler.applyDRBD runs `drbdadm primary --force`
then `drbdadm secondary`, which seeds the resource into UpToDate
without an operator running drbdadm by hand. Subsequent reconciles
see firstActivation=false and skip.
2. Server.applyObserved (events2 → ReportObserved) now actually
writes the observed DRBD state back to the Resource: DrbdState
prop + Resource.State.InUse. Lets REST clients (linstor-csi,
kubectl-linstor) see live runtime status without schema changes.
drbdadm wrapper gains PrimaryForce so the seed step uses --force
explicitly rather than the bare Primary which refuses to promote
when local disk is Inconsistent and no peer is UpToDate.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
0 commit comments