Skip to main content

Update agent

  1. Open Nodes and select the server.
  2. Go to the tab Agent.
  3. Find an agent update card.
  4. Press the new version checker.
  5. If the version is available, run the update.
Task history and current version are displayed on the same card, and the task is considered complete after the agent reconnects and reports the new version.
There is no separate button to roll back the agent to an arbitrary old version. If the replacement fails, the agent automatically restores the previous binar.

What counts as a successful agent upgrade

The task should end with confirmation from the agent with the target version. The command sent, the completion of the download or the heartbeat of the old version does not confirm the update. Check the source, the availability of the artifact and the compatibility of capabilities; for partial mass results, look at each node separately. The dashboard is updated independently: its new version may require agent capabilities that are not yet on the node.

Update selected nodes

In the list of nodes, mark the desired lines and start updating the agents for the selected set. Uses a regular step-by-step mechanism; execution continues after the page is closed. Check the result of each node. Empty selection does not mean updating the entire park.

An old agent with no kickback mechanism

Starting from the v1.7.1 panel, a compatible Agent v1.2.8 or newer without the possibility of verified self-update can go to the target release of the agent v1.3.0 or the newer through the preparatory stage. You need a standard installation of the agent for systemd, Python 3.8+ and systemd-run. If the preliminary requirements are not met, the working binary is not replaced. The mechanism retains the identity of the agent, enrollment and settings. Success requires a new heartbeat of the target version adopted by the panel and a stable launch period. If the checks fail, a local return to the previous binarnic is performed, including when communication with the panel is lost. See the result of the task: a late response of the preparatory task should not change the already completed update result.

Update the panel

  1. Open Settings → Updates.
  2. In the panel version press Check for updates.
  3. Take a look at the available version.
  4. Press Update the panel and confirm the launch.
On the same tab, you can configure the source of releases and the update channel.

If the source of updates is not available

The panel can show the last saved result with a sign of obsolescence and an error in the source. The presence of a version in such a response does not prove that the new test was successful.

Rollback

If the agent update is not confirmed by the target version, disassemble the operation report and recovery on a specific node. Do not consider the heartbeat of the old version a successful update. For the panel, there is a separate otkat database and release kit .

Verification

  • Agent: tab Agent shows the target version and fresh heartbeat.
  • Panel: Settings → Updates shows the new current version.