Issues 125 and 126: two apply-layer gaps the novox session hit live #131

2026-09-26T15:25:36Z

jschoubben commented

2026-09-26 15:25:36 +00:00

125 — a hold is not a line in the apply report. Sixteen resources held for an untaken module while push count, apply journal, status and node show all read as success; the operator stopped the edge's predecessor on their word (the route-proxy flip outage, recovered in minutes).

126 — a volume path is not in the spec comparison, and a roll-out policy makes a build a deployment. Together they turned the /var/lib data-path migration into a forge outage: gitea rolled out mid-choreography onto an empty directory, and five other modules silently kept old containers over renamed inodes. Directly corroborates #119's stated hazard — "changing where a definition looks without the data moving does not fail loudly" — with a live instance and a recovery narrative.

Filed as 119/121 inside the novox session before syncing; renumbered past the other session's 119–124.

**125 — a hold is not a line in the apply report.** Sixteen resources held for an untaken module while push count, apply journal, `status` and `node show` all read as success; the operator stopped the edge's predecessor on their word (the route-proxy flip outage, recovered in minutes). **126 — a volume path is not in the spec comparison, and a roll-out policy makes a build a deployment.** Together they turned the /var/lib data-path migration into a forge outage: gitea rolled out mid-choreography onto an empty directory, and five other modules silently kept old containers over renamed inodes. Directly corroborates #119's stated hazard — *"changing where a definition looks without the data moving does not fail loudly"* — with a live instance and a recovery narrative. Filed as 119/121 inside the novox session before syncing; renumbered past the other session's 119–124.

jschoubben added 1 commit 2026-09-26 15:25:36 +00:00

Issues 125 and 126: two apply-layer gaps the novox session hit live 7842457d4b

125: a hold is not a line in the apply report — sixteen resources held
for an untaken module while four surfaces reported success, and the
operator stopped the edge's predecessor on their word (the route-proxy
flip outage). 126: a changed volume path neither recreates a running
container nor warns, and a roll-out upgrade policy makes a build a
deployment — together they turned a data-path migration into a forge
outage (the /var/lib move). Filed as 119/121 in the novox session
before syncing; renumbered past the other session's 119-124.

jschoubben merged commit e38814962d into main

2026-09-26 15:25:41 +00:00

jschoubben deleted branch issue/125-126-from-the-novox-session

2026-09-26 15:25:41 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#131