Issue 146: what made it slow, and what was changed so it is not

2026-09-29 17:45:25 +02:00
parent f6ed3545b7
commit e9b1010bc0
1 changed files with 17 additions and 0 deletions
@@ -136,6 +136,23 @@ makes the enrolment arrive once, or stops the second arrival from rotating anyth
 the composition that cannot reach the bus at genesis). Three of the four are fixed on branches; the
 fourth is the genesis work.
 ## What made it slow, and what was changed so it is not
 Six faults behind one another, each found by raising a machine and reading what it said. What cost
 the most was not the faults:
 - **Every bed's own instructions named the bundle that cannot work**, so the first three attempts
  ended in a control plane crash-looping on a missing bus. They name the working one now.
 - **A host binary built without its system** refuses everything it is given with *this host was
  built for ""*, which reads like a broken bundle. The lab's README says so.
 - **`make image` in the control plane had been broken for as long as its base was pinned**: the
  Dockerfile's fallback is a Go older than the module asks for, and the pipeline never saw it
  because the pipeline passes the declared base in. It reads the base from the manifest now.
 - **Leaving the machine standing is what answers the question.** Every finding above came from
  shelling in afterwards — the host's log, the bus's log, the file the bus was actually handed —
  and none from the test's own output, which says only that nothing converged. The bed takes
  `MESH_LAB_KEEP`, and the README says to reach for it first.
 ## What it cost, for the next person
 Every lab bed still names `foundation-first-node.lock` in its own instructions, and that bundle