4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	31a6cf09a9	fix(host_agent): a node the operator keeps drained stays drained through its maintenance (#5777) ... #5777 "Maintenance would make a node the operator keeps drained active after its reboot". A swarm node already set to drain or pause, such as a manager kept free of work, is no longer drained before its reboot or made active after it. Its job only updates and reboots it, and back-in-service needs it ready but not active. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 20:45:22 -04:00
bvandeusenandClaude Opus 5.5	c6b15b1cc6	fix(host_agent): maintenance reads the swarm through the loaded Docker plugin, not by importing its models again (#5768) ... Importing plugins.docker.models by path defines its tables a second time, because the plugin manager loaded them as _steward_plugin_docker.models. Inside the app that raises InvalidRequestError, not ImportError. The cadence integration test hit it, and #5767's _swarm (used when a job is planned) carried the same import. Both now go through maintenance.docker_models(). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:03:59 -04:00
bvandeusenandClaude Opus 5.5	200384e52d	feat(host_agent): a group's updates and reboots on a weekly cadence, one host at a time (#5768) ... #5768 "A maintenance cadence: a group's updates and reboots, one host at a time, on a schedule". A plan names an inventory group, a weekday and time in a time zone, a window and a reboot policy (only when required by default). At its slot a run takes the group's hosts in order and gives each a #5767 maintenance job. The next host starts only when the last is back in service: its agent is posting and, for a swarm node, the node is active and every replicated service is at its replicas. A failure stops the run, and no host is started once the window has passed. A host's latest failure shows as host_agent/<host>/maintenance_failed, for an ordinary alert rule. The page is Hosts → Maintenance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 18:59:07 -04:00
bvandeusenandClaude Opus 5.5	22b0be2b6c	feat(host_agent): Steward hands a host a maintenance job and follows it through the reboot (#5767) ... #5767 "Steward hands a host a maintenance job and follows it to the end, through its own restarts", milestone 514. A host_maintenance_jobs row per job: queued → updating → [draining →] rebooting → [undraining →] done, or failed / timed_out. Steward's answer to an ingest post carries the step that host's agent should carry out now; the agent (1.18.0) leaves each step id for the root helper once, and the helper refuses an id it already ran, so repeats are harmless. Results come back as the #5766 maintenance events, matched by step id; the reboot completes when the host's `started` event has a boot_at after the reboot was handed out. The job reboots only when the update says one is needed (or never, if asked). A swarm node is drained first by itself if it's a manager or by a manager with the helper, and made active after; with no manager to drain it the job is refused. A minute tick times out a job past its state's deadline. A maintenance window over host_agent/<host> lasts the rest of the job. Everything is on the row, so a Steward restart, or the reboot of the host Steward runs on, resumes from the next post. Ingest runs it in its own savepoint so a job going wrong never costs the samples. The Agent panel leads with a running job and says what a finished one did; Manage agent has Update now (with "never reboot"), or says why a job can't start. Integration test: hand off, Steward restarts, the post-boot events close the job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 18:42:12 -04:00