Repository navigation
k3s: The prune of the Addons requires k3s, rather than k3s being up already - #20
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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