Skip to main content

Acknowledge a degraded array

POST 
/array/degraded/acknowledge

Required role: admin. Only an account or token with the admin role can call this operation.

Example request
curl --request POST \
  --header "Authorization: Bearer $HOSERVA_TOKEN" \
  "https://$HOSERVA_HOST:8008/api/v1/array/degraded/acknowledge"

Records the user's explicit choice to proceed while the array is degraded (hoserva array acknowledge-degraded): the daemon acknowledges the missing disk on its live storage gate and then runs the exact not-ready to ready transition a returning disk reaches: mounting and confirming the pool, then starting every enabled, unmasked service unit that depends on it (Samba, NFS, Docker, libvirtd), never through a shell and never by a second mechanism. The acknowledgement itself survives every later rebuild of the daemon's array sequence (a share change, a disk-topology change, a daemon reload) for as long as the same disk stays missing. Refused with array_not_degraded (409) when nothing is currently missing — acknowledging a degraded state that does not exist would let a stale acknowledgement outlive the situation it was about. Refused with array_services_not_started (409) when the acknowledgement itself succeeds but the transition it triggers does not actually start anything — the array is in maintenance mode (hoserva array stop), or mounting or confirming the pool fails — so this never reports success over services that never came up — in that refusal case arrayDegradedAcknowledged on a later getStatus still reports true (the acknowledgement stands) while storageServicesReleased stays false, so a client must check both before ever telling the user services are running. arrayDegraded on the returned status stays true for as long as the disk is still missing — acknowledging never reports a degraded array as healthy — and arrayDegradedAcknowledged becomes true instead, the field the persistent banner and top-bar pill use to show "acknowledged, running degraded" rather than clearing the warning outright.

Responses​

System status after acknowledging. arrayDegraded stays true while the disk is still missing; arrayDegradedAcknowledged is true; storageServicesReleased is true only once the transition actually started the gated services.