[session 1] docs(technical.agent): correct UPDATE_AGENT auto-restart note (4.5.x) #49

Merged
hiveiq merged 1 commits from fix/agent-update-restart-note into develop 2026-07-22 09:09:59 -04:00
Owner

Session: 1

Corrects a stale claim in the technical.agent Gotchas tab. The REBOOT section said UPDATE_AGENT swaps the JAR but does not auto-restart the JVM and needs a follow-up RESTART_AGENT.

That is wrong for agent 4.5.x. UPDATE_AGENT auto-restarts the agent process and activates the new code (UPDATE -> Restarting). Proven fleet-wide 2026-07-21 across 246 ATMs and on the BP000101 pilot (a post-update REBOOT executed the 4.5.1 code path - it would have failed at goOutOfService=-1 if the code were not live). RESTART_AGENT is only needed to bounce the agent without updating.

Also clarifies the restart is the agent process, not an ATM reboot (so fleet-wide UPDATE_AGENT is non-customer-impacting), and that agentVersion alone does not prove running code. Matches the corrected memory note from this session.

Docs-only, single tab.

Session: 1 Corrects a stale claim in the technical.agent Gotchas tab. The REBOOT section said `UPDATE_AGENT` swaps the JAR but does **not** auto-restart the JVM and needs a follow-up `RESTART_AGENT`. **That is wrong for agent 4.5.x.** `UPDATE_AGENT` auto-restarts the agent process and activates the new code (`UPDATE -> Restarting`). Proven fleet-wide 2026-07-21 across 246 ATMs and on the BP000101 pilot (a post-update REBOOT executed the 4.5.1 code path - it would have failed at `goOutOfService=-1` if the code were not live). `RESTART_AGENT` is only needed to bounce the agent *without* updating. Also clarifies the restart is the **agent process, not an ATM reboot** (so fleet-wide UPDATE_AGENT is non-customer-impacting), and that `agentVersion` alone does not prove running code. Matches the corrected memory note from this session. Docs-only, single tab.
hiveiq added 1 commit 2026-07-22 09:07:48 -04:00
The REBOOT section claimed UPDATE_AGENT swaps the JAR but does not auto-restart
the JVM and needs a follow-up RESTART_AGENT. That is wrong for agent 4.5.x:
UPDATE_AGENT auto-restarts the agent process and activates the new code
(UPDATE -> Restarting), proven fleet-wide 2026-07-21 across 246 ATMs and on the
BP000101 pilot (post-update REBOOT executed the 4.5.1 code path). RESTART_AGENT
is only needed to bounce without updating.

Also clarifies: the restart is the agent process, not an ATM reboot, so a
fleet-wide UPDATE_AGENT is non-customer-impacting; and agentVersion alone does
not prove running code (verify a behavioural marker).

Session: 1

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
johannes approved these changes 2026-07-22 09:07:53 -04:00
hiveiq merged commit 20034bb95a into develop 2026-07-22 09:09:59 -04:00
hiveiq deleted branch fix/agent-update-restart-note 2026-07-22 09:09:59 -04:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hiveiq-src/hiveops-guide#49