diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md index 90c5b28..165c8c8 100644 --- a/docs/CURRENT-STATE.md +++ b/docs/CURRENT-STATE.md @@ -1763,6 +1763,20 @@ **dc1 is NOT applied**; its plan is identical in shape (6/4/0). **STILL FLAGGED: dc0 `/var/lib/libvirt` 2.0T available vs 2.0 TiB nominal** -- all four volumes created in 0s because qcow2 is thin, but there is no room for those OSDs to FILL. +- **R1 PRECONDITION 3 CLOSED BY MEASUREMENT 2026-07-29 -- the canary re-commission is + conclusive.** Operator: "Commission storage-01 as the canary". Capture + `docs/audit/dc0-canary-commission-20260729.txt`. `maas admin machine commission kghggm + skip_networking=1` (sysid matched by PINNED BOOT MAC, never by name -- MAAS renames at + enlistment). Commissioning -> Ready in **~200s**, no timeout, no SERVFAIL. + **The full before/after diff of status, power, block devices, interfaces, MACs and links is + EXACTLY ONE HUNK: `vdb` (536870912000 bytes = 500 GiB) added to blockdevices.** links 12 -> + 12; MACs identical; links identical. All twelve static links survive with their addresses, + modes and subnets intact -- including the D-134 octet `.150` mirrored across all six planes + in both families, with the v6 host part `::150` being the 2026-07-27 D-136 mirror ruling + visible in live data. **So `skip_networking=1` preserves the network EXACTLY while storage + is still re-scanned, which is the entire point.** The amendment's concern was legitimate + (the DEFAULT path does reconfigure networking) and the vendor's own control is sufficient. + **REMAINING: dc0 storage-02/03/04, then all of dc1** (apply + the same re-commission). - **THREE PLATFORM BEHAVIOURS GRADUATED to `references/platform-traps.md`** at session close, having been recorded only in this status document (which is consolidated over time, so a durable trap does not belong here alone): MAAS auto-reserves `::1`-`::ffff:ffff` on EVERY diff --git a/docs/audit/dc0-canary-commission-20260729.txt b/docs/audit/dc0-canary-commission-20260729.txt new file mode 100644 index 0000000..997eaff --- /dev/null +++ b/docs/audit/dc0-canary-commission-20260729.txt @@ -0,0 +1,38 @@ +CANARY RE-COMMISSION -- vr1-dc0-storage-01, 2026-07-29 +====================================================== +Operator approval: "Commission storage-01 as the canary". Run from voffice1. This is the +empirical close of R1 precondition 3, which the D-121 amendment said must be verified +BEFORE the apply and which had until now only been answered from the API's own help text. + +MACHINE: sysid kghggm, MAAS hostname `first-oryx` (MAAS renames at enlistment -- matched +by PINNED BOOT MAC 52:54:00:5f:8d:42, never by name). + +COMMAND (skip_storage deliberately UNSET so storage IS re-scanned): + maas admin machine commission kghggm skip_networking=1 + +TIMELINE: Commissioning -> Ready in ~200s. No timeout, no SERVFAIL. (For contrast, the +2026-07-21 pre-D-131 failures were seven consecutive 30-minute timeouts.) + +RESULT -- the full before/after diff of status, power, block devices, interfaces, MACs and +links is EXACTLY ONE HUNK: + + "blockdevices": [ ["vda", 590558003200], + + ["vdb", 536870912000] ] + + links BEFORE/AFTER : 12 / 12 + MACs identical : True + links identical : True + +536870912000 bytes = 500 GiB exactly -- the volume R1's apply created. + +WHAT THIS SETTLES. `skip_networking=1` preserves the network configuration EXACTLY: all 12 +static links survive with their addresses, modes, subnets and per-interface MACs unchanged, +including the D-134 octet .150 mirrored across all six planes in both families (the v6 host +part ::150 is the 2026-07-27 D-136 mirror ruling, visible here in live data). Meanwhile +storage IS re-scanned and the new device enters MAAS's inventory, which is the entire point. + +Precondition 3 is now closed by MEASUREMENT rather than by reading the API help. The +amendment's concern was legitimate -- the DEFAULT commissioning path does reconfigure +networking -- and the vendor's own control is sufficient. + +NOT YET DONE: the other three dc0 storage nodes (storage-02/03/04), and all of dc1. diff --git a/docs/changelog-20260728-vip-arity-gate.md b/docs/changelog-20260728-vip-arity-gate.md index 52b4272..a7c5f04 100644 --- a/docs/changelog-20260728-vip-arity-gate.md +++ b/docs/changelog-20260728-vip-arity-gate.md @@ -913,3 +913,21 @@ **NOT DONE, gated separately:** the re-commission (`maas admin machine commission skip_networking=1`), and dc1 entirely. + +## 36. Canary re-commission -- R1 precondition 3 closed by measurement + +Operator: **"Commission storage-01 as the canary"**. `maas admin machine commission kghggm +skip_networking=1`, sysid matched by pinned boot MAC. Ready in ~200s. + +**The entire before/after diff is one hunk: `vdb` (500 GiB exactly) added to blockdevices.** +links 12 -> 12, MACs identical, links identical. Every static address, mode and subnet +survives -- including the `.150` octet mirrored across six planes in both families. + +Precondition 3 was previously answered from the API's help text; it is now answered by +measurement. The concern was legitimate (the default path DOES reconfigure networking) and +`skip_networking=1` is sufficient. + +**Revert.** None applicable -- commissioning is idempotent and re-runnable; the node +returned to Ready with its configuration intact. + +**Remaining:** dc0 storage-02/03/04, then dc1 (apply + re-commission).