Updater cannot detect or repair per-binary version skew #1413

Closed
opened 2026-10-27 13:40:18 +00:00 by sam · 0 comments
Owner

archie-update-install is component-driven: it compares ARCHIE_UPDATE_{DAEMON,AGENT}_PREVIOUS against _VERSION and acts only when they differ. It has no notion of the versions of the individual installed binaries.

Two consequences found on carina (2026-09-17), updating 1.24.0 -> 1.26.0:

  1. Self-healing is impossible. With the daemon already at the target version the installer reports 'no approved component changes; nothing to install' -- even while archie-ui, archie-gateway and archie-state-store sit on older binaries. A drifted host stays drifted; the only repair is to induce a fake version delta.

  2. This host WAS drifted, badly, and nothing noticed: archie-ui was at 1.27.0 (ahead of the daemon), archie-gateway at 1.21.3, archie-state-store at 1.21.0, while archied reported 1.24.0. Mixed versions share the state store and NATS, and the state-store wire contract (docs/prds/state-store-contract.md) is version-sensitive, so this is a latent correctness risk, not just untidiness.

Suggested fix: after installing, compare each binary's own '-version' output (or a build stamp) against the target and treat a mismatch as work to do; surface the per-binary versions in the update report rather than a single per-component version. Also worth deciding whether the check should run on a schedule so drift is reported rather than accumulating silently.

Close reason

Closed


Imported from beads archie-core-k94o · GitHub #836 · type bug · priority P2 · created 2026-09-17 · closed 2026-09-22

archie-update-install is component-driven: it compares ARCHIE_UPDATE_{DAEMON,AGENT}_PREVIOUS against _VERSION and acts only when they differ. It has no notion of the versions of the individual installed binaries. Two consequences found on carina (2026-09-17), updating 1.24.0 -> 1.26.0: 1. Self-healing is impossible. With the daemon already at the target version the installer reports 'no approved component changes; nothing to install' -- even while archie-ui, archie-gateway and archie-state-store sit on older binaries. A drifted host stays drifted; the only repair is to induce a fake version delta. 2. This host WAS drifted, badly, and nothing noticed: archie-ui was at 1.27.0 (ahead of the daemon), archie-gateway at 1.21.3, archie-state-store at 1.21.0, while archied reported 1.24.0. Mixed versions share the state store and NATS, and the state-store wire contract (docs/prds/state-store-contract.md) is version-sensitive, so this is a latent correctness risk, not just untidiness. Suggested fix: after installing, compare each binary's own '-version' output (or a build stamp) against the target and treat a mismatch as work to do; surface the per-binary versions in the update report rather than a single per-component version. Also worth deciding whether the check should run on a schedule so drift is reported rather than accumulating silently. ### Close reason Closed --- _Imported from beads `archie-core-k94o` · GitHub #836 · type bug · priority P2 · created 2026-09-17 · closed 2026-09-22_
sam added the mediumbug labels 2026-10-27 13:40:18 +00:00
sam self-assigned this 2026-10-27 13:40:18 +00:00
sam closed this issue 2026-10-27 13:40:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1413