MAAS PROFILE / REGION RESOLUTION -- dc0 per-DC region migration (D-132 q1)
Captured 2026-07-30 ON voffice1 (D-128 Plane-2 host). Read-only.
======================================================================

-- profile store (measured, not assumed) --
-rw-r--r-- 1 jessea123 jessea123       0 Jul 29 07:26 /home/jessea123/.maascli.db
-rw------- 1 jessea123 jessea123 1093632 Jul 30 20:02 /home/jessea123/snap/maas/current/.maascli.db

NOTE: the LIVE profile store is ~/snap/maas/current/.maascli.db (snap-confined,
per-revision -- the same refresh fragility already recorded for the SEC-012
power key). The zero-byte ~/.maascli.db is inert residue.

-- profile -> region URL (names + URLs only; no credential material) --
admin            -> http://10.10.0.20:5240/MAAS/api/2.0/
vr1-dc0-region   -> http://127.0.0.1:5241/MAAS/api/2.0/

-- discriminator: machine count + rack-controller identity --
profile=admin machines=23 racks=voffice1,vvr1-dc0,vvr1-dc1
profile=vr1-dc0-region machines=0 racks=hot-kid

-- scripts/maas-profile-assert.sh, live, BOTH directions --
$ maas-profile-assert.sh vr1-dc0-region hot-kid
OK   profile 'vr1-dc0-region' -> region with racks [hot-kid] (as expected)
  exit=0

$ maas-profile-assert.sh admin voffice1,vvr1-dc0,vvr1-dc1
OK   profile 'admin' -> region with racks [voffice1,vvr1-dc0,vvr1-dc1] (as expected)
  exit=0

$ maas-profile-assert.sh admin hot-kid      # NEGATIVE -- must fail
FAIL profile 'admin' resolves to the WRONG region
     expected racks: [hot-kid]
     actual   racks: [voffice1,vvr1-dc0,vvr1-dc1]
  exit=1

-- harness --

maas-profile-assert: 20 passed, 0 failed