|
LIVE: MAC adoption applied, controllers commissioned, all ruled MAAS tags created
Operator: 'Commission and process all the listed tasks.' Four gated mutations, sequenced deliberately. MAC adoption FIRST, while the VMs were idle -- commissioning power-cycles them and an in-place domain update must not race that. Both roots 0 add / 1 change / 0 destroy with zero creates and destroys; then MAC drift 0 across all 20 nodes and both roots re-plan 'No changes'. The pins are now real in state: until this apply the config asserted them but state did not record them, so they protected nothing. Both controllers commissioned on the DEFAULT path -- deliberately not skip_networking=1, since unlike the storage nodes they had no configuration to preserve. Both New -> Ready in ~200s. Power control was the only thing missing, which confirms the earlier diagnosis by measurement. All ruled tags created and applied, every write read back. dc0 created all four; dc1 correctly reused the three global role tags and created only juju-controller-vr1-dc1. Twenty nodes tagged. Independently verified from MAAS rather than from script output: fleet 22 = 20 Ready + 2 Deployed, no New remaining; control 6 / compute 4 / storage 8 / juju-controller-vr1-dc0 1 / juju-controller-vr1-dc1 1 / openstack-vr1-dcN 9 each. check PASSES on both DCs. THE STAGE-5 ALLOCATION BLOCKER IS CLOSED: every tag the bundle machines block constrains on now exists and is applied. Gauntlet ALL GREEN (87) on vcloud; repo-lint 0 fail. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| docs/CURRENT-STATE.md |
|---|
| docs/changelog-20260728-vip-arity-gate.md |
|---|