fix: [nomad-step-5] S5.2 — nomad/jobs/staging.hcl + chat.hcl (#989) #999
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#999
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-989-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #989
Changes
AI Review
Blocker
critical
lib/init/nomad/cluster-up.sh:site-contenthost volume added tonomad/client.hcl(path/srv/disinto/docker) but NOT added to theHOST_VOLUME_DIRSarray incluster-up.sh.nomad/AGENTS.md(lines 48–56) documents this exact two-file constraint: "Adding a host_volume block there requires adding its path here so the dir exists before nomad starts (otherwise client fingerprinting fails and the node stays in 'initializing')".chat-historywas correctly added in a prior PR (line 69);site-contentwas not added here.Fix: add
"/srv/disinto/docker"toHOST_VOLUME_DIRSinlib/init/nomad/cluster-up.sh.Confirm closed:
grep -q '/srv/disinto/docker' lib/init/nomad/cluster-up.shpasses.Advisory
info
nomad/jobs/chat.hcl+bin/disinto:vault-seed-chat.shis referenced inchat.hclcomments and theelsebranch warning, andbin/disintowireschat) seed_name="chat" ;;— buttools/vault-seed-chat.shdoes not exist. Theif [ -x "$seed_script" ]guard means no runtime failure; the seed is silently skipped. Track for the step that adds vault seeding for chat.info
nomad/AGENTS.md(lines 13–21): the jobspec table documents all committed jobs but doesn't includestaging.hclorchat.hcl. Minor; can be a drive-by update in the fix commit.Verdict
REQUEST_CHANGES — site-content host volume added to client.hcl but missing from cluster-up.sh HOST_VOLUME_DIRS — fresh-box init will fail to fingerprint the volume and staging will not schedule
Reviewed at
da93748| AGENTS.mdAI Review: REQUEST_CHANGES — site-content host volume added to client.hcl but missing from cluster-up.sh HOST_VOLUME_DIRS — fresh-box init will fail to fingerprint the volume and staging will not schedule
AI Re-review (round 2)
Previous Findings\n- critical
lib/init/nomad/cluster-up.sh:/srv/disinto/dockermissing fromHOST_VOLUME_DIRS→ FIXED: line 69 adds it in correct position between caddy-data and chat-history.\n- infonomad/AGENTS.md: staging.hcl and chat.hcl entries missing from jobspec table → FIXED: both rows added.\n\n### Verdict\nAll prior blockers closed. No new issues introduced by the fixup hunk.Verdict
APPROVE — Prior blocker closed: /srv/disinto/docker added to HOST_VOLUME_DIRS; AGENTS.md advisory also addressed.
Reviewed at
8b1857e| Previous:da93748| AGENTS.mdAI Re-review (round 2): APPROVE — Prior blocker closed: /srv/disinto/docker added to HOST_VOLUME_DIRS; AGENTS.md advisory also addressed.