|
dc0 MAAS region VM APPLIED, MACs pinned, converged; commissioning trap recorded
Capacity gate re-measured PASS (RAM 870/1024 = 85%, FIT, 154 GiB headroom). Plan asserted on content -- exactly two resources, both the new VM. Applied 2 added / 0 changed / 0 destroyed; MACs measured and pinned; converged ZERO DIFF with live virsh domiflist byte-identical to the pin; virsh power set. Enlisted as hot-kid / tw7ptw. Corrected against measurement: the "1 add" figure in both new comments and in D-104's amendment prose is wrong at resource level -- node-vm creates a domain AND a volume, so it is 2 to add. The half that mattered, 0 change / 0 destroy, held. Ordering trap measured and recorded as a standing rule: the first apply sets running=true, so the VM PXE-enlists and auto-commissions within ~90s, and pinning MACs is an in-place libvirt_domain update that BOUNCES the guest -- stalling that commission at "Loading ephemeral". After pinning MACs on a freshly-applied VM, assume commissioning was interrupted and re-commission deliberately. Recovery is abort -> New -> commission. dc1's region VM is authored but NOT applied. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| docs/CURRENT-STATE.md |
|---|
| docs/changelog-20260730-stage5-open.md |
|---|