Batch 1 all Ready; the New detour was ORDERING, not chance
Batch of three enlisted in 2.3 min against a 15-minute zero-record stall for
nine, and all three went straight to Ready with no New detour -- because
power was set BEFORE commission was issued, where the canary was
commissioned first and powered afterwards.

That supersedes the earlier 'one-off' reading with a stronger and more
useful conclusion: the detour is caused by ordering. Revised standing
procedure is delete -> virsh start -> self-enlist -> SET POWER -> abort ->
commission, and never commission a machine whose power_type is unset.

Region now holds 4 machines all Ready, each matched to its libvirt domain by
pinned MAC.

Role tags need no new tool: maas-role-tags.sh creates the four missing ones
and refuses while any pinned MAC lacks a record, so it enforces the ordering
itself.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf
1 parent 72159e3 commit 5ff632d9edafbdda75697caabda20cffe638baad
@JANeumatrix JANeumatrix authored 22 hours ago
Showing 2 changed files
View
docs/CURRENT-STATE.md
View
docs/changelog-20260730-dc0-region-migration.md