Fleet and Elastic Agent 8.1.2edit

Review important information about the Fleet and Elastic Agent 8.1.2 release.

Known issuesedit

Elastic Agent upgrade may fail with agent binary verification error


During an Elastic Agent upgrade, agent binary verification may fail with the following message:

[elastic_agent][error] failed to dispatch actions, error: failed verification of agent binary: 2 errors occurred:
fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.asc: no such file or directory
open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.sha512: no such file or directory

This is the result of a known issue.


After upgrade, the agent status changes to Unhealthy, and Elastic Agent no longer sends data. To fix this problem:

  • If you are using Elastic Agent version 8.1.0 or earlier, continue using that version until you can upgrade directly to 8.2.x.
  • If you are using an affected version of Elastic Agent, reinstall a non-affected version.

Bug fixesedit

  • There are no bug fixes for Fleet in this release.
Elastic Agent
  • Propagate input ID from the Agent policy into the Filebeat configuration. Note that no validation is performed on this field. #30386