|
G17 opened by operator ruling; Stage 4 DoD bullets 5-6 repaired (DOCFIX-204)
RULING (GA-R5), 2026-07-27. Question as presented: "The node-side half of bullet 5. Nodes are powered off by the READY-handoff ruling, so no node-side probe can run as things stand. Either a gated rescue-boot check on one node per DC now (closes it inside Stage 4), or split it into its own gate row targeted at Stage 5 first boot (GA-R6 E3 explicitly permits this; a conditional close is not permitted)." Operator answer, exact utterance: "split it into its own gate row". Recorded in the G17 row of docs/CURRENT-STATE.md (the authority); pushed before dependent work. G17 "Per-DC artifact source reachable FROM A NODE", [V], OPEN. dc0 -> curl 200 from a booted node against the D-135 item-1 mirror; dc1 -> apt fetches through the proxy at 10.12.68.4:3142, since dc1's ruled path is the CACHING PROXY with no node-facing mirror (D-135 amendment) and checking it as one fails by design. Trigger: Stage 5 first boot. The row states that G17 is NOT a Stage-5 precondition -- Stage 5's bootstrap needs open edge egress for the juju agent stream and snaps (D-135 items 2-3 unbuilt), a different path from the apt artifact source. Stage 4 retains bullet 5's rack-side half: the source answers on its own address with an attested-current sync. dc1's proxy PASSES; dc0 pends the sync re-run. DOCFIX-204 -- bullet 6 was UNSATISFIABLE and its stale text had spread to four surfaces. "NTP from the DC's own OPNsense edge working" is superseded by D-129(iv) (RULED 2026-07-21, "Keep MAAS hierarchy", no NTP role on the edge): the DoD asked for confirmation the edge is the time source, which the ruling had already refused, so a correctly-built DC could never meet it. Repaired in the phase-3 DoD (bullet 6 struck, bullet 5 rewritten per-DC), the phase-3 Step 7 (REWRITTEN -- it branched on gap #5 that D-135 resolved, applied one mirror check to both DCs which fails on dc1 by design, and asked for checks "from a deployed node" that the READY handoff makes impossible), the workflow-doc Gate cell (which also still said "Nodes deployed", contradicting DOCFIX-200), the buildout design, and the phase-4 prerequisites (same "nodes Deployed" error -- exactly the expectation DOCFIX-200 removed to stop Stage 5 breaking). phase-4 also gains a block making it the OWNER of G17's captures, warning that first boot is the observation window and missing it forces a deliberate rescue-boot. Text and gate-record only; no live state touched. repo-lint 0-fail. DOCFIX next-free -> 205. Revert: git revert this commit; all changes are documentation and the G17 gate row. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| docs/CURRENT-STATE.md |
|---|
| docs/changelog-20260727-creds-consolidation.md |
|---|
| docs/dc-dc-buildout-design.md |
|---|
| docs/dc-dc-deployment-workflow.md |
|---|
| docs/session-ledger.md |
|---|
| runbooks/dc-dc-phase3-maas-enlist-deploy.md |
|---|
| runbooks/dc-dc-phase4-juju-bundle-per-dc.md |
|---|