Issue 332: the service manager could neither clear a failed unit nor say what wants it #222

Merged
mesh-admin merged 2 commits from issues/332-the-service-manager-cannot-clear-or-explain-a-failed-unit into main 2026-10-08 15:52:55 +00:00
Contributor

Registers issue 332 (playbook 03), status located. The node-service-manager seat had no verb to clear a failed unit's record (systemctl reset-failed), or to say what wants a unit and whether an enable link naming it dangles. The only step left was a shell, which ADR 0245 rules out.

The fix lands in the three steps of ADR 0246:

  1. mesh-controller #158 promises reset-failed and wanted-by as optional.
  2. mesh-catalog #137: the systemd module serves them, merged after step 1 is delivered.
  3. A later controller change requires them.

fixed-by: is filled at resolution. merge-check.sh passes locally.

Registers issue 332 (playbook 03), status `located`. The `node-service-manager` seat had no verb to clear a failed unit's record (`systemctl reset-failed`), or to say what wants a unit and whether an enable link naming it dangles. The only step left was a shell, which ADR 0245 rules out. The fix lands in the three steps of ADR 0246: 1. mesh-controller #158 promises `reset-failed` and `wanted-by` as optional. 2. mesh-catalog #137: the systemd module serves them, merged after step 1 is delivered. 3. A later controller change requires them. `fixed-by:` is filled at resolution. `merge-check.sh` passes locally.
mesh-admin added 1 commit 2026-10-08 15:28:24 +00:00
Issue 332: the service manager could neither clear a failed unit nor say what wants it
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
c3a20baece
A leftover user unit stayed raised on the workstation: no seat verb showed
the dangling enable link that keeps asking for it, or reset its failed
record, so the only step left was a shell. Lands per ADR 0246.
Author
Contributor

Delivery novox/hq@fd6c452e619f — delivered since 2026-10-08T15:53:04Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-08 15:40 (new) → proposed (announced): novox/hq#222's head announced
  • 2026-10-08 15:42 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 15:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 15:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 15:53 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@fd6c452e619f` — **delivered** since 2026-10-08T15:53:04Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 15:40 (new) → proposed (announced): novox/hq#222's head announced - 2026-10-08 15:42 proposed → checked (checked): the verdict names this commit - 2026-10-08 15:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 15:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 15:53 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-08 15:40:03 +00:00
Issue 332: add unlink-dangling and the glob refusal from the review
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
fd6c452e61
disable cannot remove a link whose unit file is gone, so the verb that
finds it needed one that removes it.
mesh-admin merged commit acc82aa5e4 into main 2026-10-08 15:52:55 +00:00
mesh-admin deleted branch issues/332-the-service-manager-cannot-clear-or-explain-a-failed-unit 2026-10-08 15:52:55 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#222