|
maas-role-tags owns the D-104 controller tag too; harness 11 -> 12
The per-DC Juju controller carries its OWN tag and none of the role tags, so a bootstrap constrained on tags=juju-controller-<dc> targets it deterministically and no OpenStack role constraint can cross-grab it. The script used to SKIP it as 'not a role node'; it now emits that tag as the host role, so every stage -- existence check, NEED/HAS, apply, read-back -- handles it with no special case. Doing it in the script rather than as two one-off maas commands is the direct consequence of the 2026-07-29 ruling that these assignments follow ALL DC deployments: a one-off command does not travel to the next standup. T10 re-pointed (the controller is TAGGED, not skipped) and T10b added so a missing controller tag is gated like the three role tags. Owned: my first attempt put an apostrophe inside the single-quoted shell string wrapping the python block, so bash parsed python and every case failed. Reworded; the block now carries none. Gauntlet ALL GREEN (87) on vcloud. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| scripts/maas-role-tags.sh |
|---|
| tests/maas-role-tags/run-tests.sh |
|---|