IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Fleet and Elastic Agent 8.1.1edit
Review important information about the Fleet and Elastic Agent 8.1.1 release.
Known issuesedit
Elastic Agent upgrade may fail with agent binary verification error
Details
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.
Impact
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
- Fleet
-
- Add a new validation message. #127239
- Fix empty assets on package install. #127070
- Hide enroll command when user creates a new agent policy in the Add agent flyout. #126431
- Make input IDs unique in agent policy yaml. #127343
- Fix links to Agent logs for APM, Endpoint, Synthetics, and OSQuery. #127480
- Elastic Agent