fix(web-arm): onecli-db-password oneshot — LoadCredential + setup ordering #341
No reviewers
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos!341
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lab/20260814-1419"
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?
First activation of #339 on web-arm failed: the oneshot runs as
User=postgresbut the sops secret is root-owned 0400 —cat: /run/secrets/onecli-db-password: Permission denied— sopodman-onecliwent down withresult 'dependency'.Two changes to the oneshot:
$CREDENTIALS_DIRECTORY/db-password. Changing the unit also means switch-to-configuration restarts it on deploy, so the failed unit heals on its own.after = postgresql-setup.serviceadded alongsidepostgresql.target: the target ordering protects a cold boot, but on a live switch the target is already active and the oneshot can race the role creation (PR #339 review CONCERN 1's residual case).Deploy note:
podman-onecli.serviceitself is unchanged, so after the switch it stays dead until started once —systemctl start podman-onecli(or the next reboot).Closes #340