VersionControl:PRs/maybelle-config/272: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
cryptograss/maybelle-config#272, as GitHub has it |
cryptograss/maybelle-config#272, as GitHub has it |
||
| Line 16: | Line 16: | ||
|deploy=redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live) | |deploy=redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live) | ||
}} | }} | ||
<pre class="pr-body">The hunter redeploy after #270 failed at `caddy : Deploy Caddyfile`: | |||
``` | |||
AnsibleUndefinedVariable: 'dict object' has no attribute 'port_range_start' | |||
``` | |||
#270 renamed the emergents' `kind` from `agent` to `emergent`. `Caddyfile.hunter.j2` still skipped only `kind: agent`, so the three emergent containers went into the port-range loop, and they have no `port_range_start`. My miss: when I checked #270, I rendered the compose template for all four containers but not the Caddyfile. | |||
The fix is one line: skip `('emergent', 'agent')`. `agent` stays in the list until the rename's last step, the same way `container_startup.py` handles it. A grep of the deploy logic finds no other `kind` check left on `'agent'` alone. | |||
**Checked:** I rendered `Caddyfile.hunter.j2` with Jinja's StrictUndefined against production's `hunter/ansible/inventory.yml`. The old template fails with this exact error. The fixed one renders 100 lines, with one port block, workbench's (14100–14109), and none for emergent-magent, emergent-re or emergent-blu. | |||
Deploy: redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live) | |||
Worked on by: magent, Justin, in #emergence</pre> | |||
Latest revision as of 17:06, 9 November 2026
| State | 🟣 merged 2026-11-02 22:59:52 |
|---|---|
| Worked on by | magent, justin |
| Moods | #emergence |
| Deploy | redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live) |
| Branch | caddy-emergent-kind → production, by magent-cryptograss
|
| Opened · last pushed | 2026-11-02 22:56:13 · 2026-11-02 22:56:02 |
The hunter redeploy after #270 failed at `caddy : Deploy Caddyfile`:
```
AnsibleUndefinedVariable: 'dict object' has no attribute 'port_range_start'
```
#270 renamed the emergents' `kind` from `agent` to `emergent`. `Caddyfile.hunter.j2` still skipped only `kind: agent`, so the three emergent containers went into the port-range loop, and they have no `port_range_start`. My miss: when I checked #270, I rendered the compose template for all four containers but not the Caddyfile.
The fix is one line: skip `('emergent', 'agent')`. `agent` stays in the list until the rename's last step, the same way `container_startup.py` handles it. A grep of the deploy logic finds no other `kind` check left on `'agent'` alone.
**Checked:** I rendered `Caddyfile.hunter.j2` with Jinja's StrictUndefined against production's `hunter/ansible/inventory.yml`. The old template fails with this exact error. The fixed one renders 100 lines, with one port block, workbench's (14100–14109), and none for emergent-magent, emergent-re or emergent-blu.
Deploy: redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live)
Worked on by: magent, Justin, in #emergence