8000 k3s: The prune of the Addons requires k3s, rather than k3s being up already by andsens · Pull Request #20 · nixos-homelab/shared · GitHub
[go: up one dir, main page]

Skip to content

k3s: The prune of the Addons requires k3s, rather than k3s being up already - #20

Merged
andsens merged 1 commit into
mainfrom
prune-requires
Nov 15, 2026
Merged

andsens merged 1 commit into
mainfrom
prune-requires

Conversation

@andsens
@andsens andsens commented Nov 15, 2026
Copy link
Copy Markdown
Collaborator

A deploy that changes the links failed the first time and worked the second: switch-to-configuration starts
each unit in a job of its own, iterating a HashMap (switch-to-configuration-ng's main.rs at the pinned nixpkgs),
so k3s-prune-addons' start could come while k3s was stopped and its start not queued yet. With Requisite=, systemd
then failed it at once ("k3s service is inactive", "Dependency failed for Delete the Addons...", result
dependency; the NAS journal of 2026-11-15 22:54:28 and 2026-11-16 00:23:44), and the switch exited 4.

Requires= queues k3s' start with the prune's, After= waits for it. A test does what the switch does: k3s and the
prune stopped, then the prune started on its own. It fails with Requisite= (the same journal lines) and passes now.

Checked: deadnix, manifests; the k3s VM test passes with the change, and fails at the new subtest with Requisite= put back. One earlier run failed in the metrics-server subtest before reaching it (pod not Ready in 300 s, intermittent; the same subtest failed #17's first CI run).

🤖 Generated with Claude Code

…lready

A deploy that changes the links failed the first time and worked the second: switch-to-configuration starts
each unit in a job of its own, iterating a HashMap (switch-to-configuration-ng's main.rs at the pinned nixpkgs),
so k3s-prune-addons' start could come while k3s was stopped and its start not queued yet. With Requisite=, systemd
then failed it at once ("k3s service is inactive", "Dependency failed for Delete the Addons...", result
dependency; the NAS journal of 2026-11-15 22:54:28 and 2026-11-16 00:23:44), and the switch exited 4.

Requires= queues k3s' start with the prune's, After= waits for it. A test does what the switch does: k3s and the
prune stopped, then the prune started on its own. It fails with Requisite= (the same journal lines) and passes now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@andsens
andsens enabled auto-merge (squash) November 15, 2026 23:45
@andsens
andsens merged commit ff8515f into main Nov 15, 2026
2 checks passed
@andsens
andsens deleted the prune-requires branch November 15, 2026 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0