Raise a machine that refuses or only partly applies its declarations past one apply interval (issue 233) #261
Closed
mesh-admin
wants to merge 2 commits from
fix/233-a-failed-probe-fails-only-what-needs-the-tool into main
pull from: fix/233-a-failed-probe-fails-only-what-needs-the-tool
merge into: :main
:main
:fix/sweep-2026-10-30
:fix/checker-full-failure
:feat/1945-user-list-switch
:fix/1945-mesh-grants-publishes-memberships
:fix/issued-states-follow-the-module
:fix/1945-credential-on-assignment
:fix/r6-mirror-on-change
:fix/store-forge-address
:fix/r6-look-again-after-unlock
:fix/r6-key-waits-said
:fix/1931-reconnects-verb
:fix/forge-requires-no-status
:fix/906-lease-renewal
:feat/r4e-controller
:fix/1106-sdk-member-merges
:fix/1399-person-word-test
:fix/1652-checks-wait
:feat/files-through-the-store-files-verbs
:fix/1649-held-ask-handed-out-twice
:fix/1658-sdk-items
:fix/1334-a-bus-reload-fails-a-tier
:feat/chain-on-the-bus
:fix/701-a-name-nothing-answers-is-not-used
:fix/270-a-dead-bus-watch-is-heard
:fix/630-config-values-from-four-sources
:fix/613-node-smb-server
:feat/328-libraries-and-module-users
:feat/325-identities-and-kept-folders
:feat/bus-view-principal
:test/plan-diff-left-out-line
:fix/the-registry-trust-test-reads-the-runtimes-module
:fix/the-runtime-file-is-the-runtimes
:feat/build-edges-are-recorded
:fix/several-contributions-collide-in-grants-v2
No Reviewers
No labels
Milestone
No items
No Milestone
Assignees
agent-ace
agent-g14
agent-novox
agent-shanks
jschoubben
mesh-tools
miel.truyen
nox-agent
Clear assignees
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: novox/mesh-controller#261
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
A new row S21 in the signals table adds the condition
apply-failingon the machine. It is raised once a machine's reports have said the same failure (refused whole, or applied only in part) for longer than one apply interval (5 minutes, the node-engine's ReconcileEvery), over at least two reports. It is not raised while the machine is silent or asleep, because S1 covers that, and a clean apply clears it. It reads the failing-since and count the store already keeps (issue 065,NotDoingWhatTheyWereTold), so there is no schema change.When the node-engine names a package manager that does not answer (key
the package manager (pacman), mesh-host PR on the same branch name), the condition names the tool in the summary and the headline (" cannot install packages"). The probe's words go in the evidence (Said), so the configuration file's path stays out of the summary. Otherwise it gives the refusal or the failed resource ids, with the machine's words in the evidence. Plain words are registered as a fallback.Why
Issue 233, question 3, decided 2026-10-11: a machine whose declarations are refused, or applied only in part, for longer than one apply interval raises a condition by itself (issue 187's family). On 2026-10-04 a workstation refused every declaration for 90 minutes, and the only sign was a line in
status.How it was tested
apply_failing_test.go: a machine whose package manager has not answered for 90 minutes is raised. The test checks the key, that the summary names pacman and the count and carries no path, that the evidence carries the probe's words, and the plain words. A whole refusal is also raised. A single report (a laptop back after a week) and a silent machine are not raised.sh merge-check.sh: green (the store tests were skipped locally because no MESH_TEST_POSTGRES is set; the build seat runs them).The first commit carried a controller binary by mistake. The second commit removes it, so the PR's diff is clean. Squash-merging leaves it out of history.
Fixes issue 233
Delivery
novox/mesh-controller@2043b0273edf— stopped since 2026-10-12T12:50:43ZDelivery plan — builds mesh-controller → novox; no bus step
Group
fix/233-a-failed-probe-fails-only-what-needs-the-tool, in order: novox/mesh-host@cb0a07ba7a → novox/mesh-controller@2043b0273eTransitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
2043b027mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on g14 as
build-1791808414964274385(builds --log build-1791808414964274385).