mirror of
https://scm.tikali.ai/tikali/applications/monky/monky-deployd.git
synced 2026-09-18 05:36:15 +00:00
mdella
43615a6fda
Three faults from one agent-managed onboarding (env-dev-08, 2026-09-09), each of which pointed the diagnosis away from the actual fault. 1. install.sh granted the agent's read on the ziti identity with a POSIX ACL. ziti-edge-tunnel rewrites that file on a controller config update and the rewrite drops the ACL: the agent applied cleanly at 01:21 and was failing every tick by 01:32. Group membership survives the rewrite (the file stays ziti:ziti 0640), so install.sh and the package postinstall now add monky-deployd to the `ziti` group, and a default ACL on the identity directory carries the grant onto a newly created file. The explicit ACLs stay for the boxes that need them. 2. openziti.load() accepts an unreadable or malformed identity: the C SDK logs "configuration is invalid" and returns a context that only fails at dial, as a bare TypeError, which the transport reported as a missing intercept or a policy gap. The SDK transport now reads and parses the identity itself and names the real fault first. 3. The disk pre-flight ran only when the bundle declared disk_need_bytes, so a bundle without one died mid-pull with containerd's "no space left on device" — which reads as a registry fault. A bundle that declares no size now has to clear the headroom floor, and the pre-flight measures containerd's root as well as the docker data-root: docker 29 keeps image layers in the containerd image store, and on env-dev-08 those sat on different filesystems (93 GiB free where the agent looked, 2.8 GiB where the pull wrote). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KLB7jieMNRkTsJ2epr4Ds1
28 lines
1.6 KiB
Bash
Executable File
28 lines
1.6 KiB
Bash
Executable File
#!/bin/sh
|
|
set -e
|
|
# service account + dirs
|
|
if command -v systemd-sysusers >/dev/null 2>&1; then
|
|
systemd-sysusers /usr/lib/sysusers.d/monky-deployd.conf || true
|
|
else
|
|
getent passwd monky-deployd >/dev/null || useradd --system --home-dir /var/lib/monky-deployd --shell /usr/sbin/nologin monky-deployd
|
|
fi
|
|
if command -v systemd-tmpfiles >/dev/null 2>&1; then
|
|
systemd-tmpfiles --create /usr/lib/tmpfiles.d/monky-deployd.conf || true
|
|
fi
|
|
install -d -m 0700 -o monky-deployd -g monky-deployd /var/lib/monky-deployd
|
|
install -d -m 0750 -o root -g monky-deployd /etc/monky-deployd
|
|
# the agent drives docker compose: docker group membership (no root)
|
|
if getent group docker >/dev/null; then usermod -a -G docker monky-deployd || true; fi
|
|
# the agent reads the host's ziti identity (owned by the tunneller, mode 0640). ziti-edge-tunnel
|
|
# REWRITES that file whenever the controller sends a config update, and the rewrite drops any
|
|
# POSIX ACL granting the agent read — group membership is the grant that survives it.
|
|
# (env-dev-08, 2026-09-09: the agent went from applied to "no intercept" 6 minutes after a refresh.)
|
|
if getent group ziti >/dev/null; then usermod -a -G ziti monky-deployd || true; fi
|
|
# the venv is relocatable only to the path it was built at; refuse a broken interpreter early
|
|
/opt/monky-deployd/venv/bin/python -c 'import monky_deployd' || { echo "monky-deployd: venv unusable (python3 mismatch?)" >&2; exit 1; }
|
|
if [ -d /run/systemd/system ]; then
|
|
systemctl daemon-reload || true
|
|
# do NOT enable the timer here: install.sh / the ansible role do it after the config exists
|
|
fi
|
|
exit 0
|