Skip to content

Conversation

@ebeahan
Copy link
Member

@ebeahan ebeahan commented Nov 6, 2025

What does this PR do?

Adds #10994 to the known issue list with work around and affected versions.

Why is it important?

Elastic Agent will fail to apply custom Agent Binary Download settings from the Fleet policy.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@ebeahan ebeahan requested review from cmacknz and pchila November 6, 2025 16:58
@ebeahan ebeahan requested a review from a team as a code owner November 6, 2025 16:58
@ebeahan ebeahan added docs skip-changelog backport-active-all Automated backport with mergify to all the active branches labels Nov 6, 2025
@mergify mergify bot assigned ebeahan Nov 6, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2025

🔍 Preview links for changed docs

pchila
pchila previously approved these changes Nov 6, 2025
@ebeahan ebeahan changed the title [docs] Adding #10994 to known issue list [docs] Adding #10994 to known issues list Nov 6, 2025
Copy link
Contributor

@colleenmcginnis colleenmcginnis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some suggestions/questions below.


```shell
# --force is needed for fleet managed agents
sudo elastic-agent upgrade 9.1.7 --force --source-uri file:///path/to/files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we hold this PR until 9.1.7 is released?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use any version in the example, but the fix will be avaiable in 9.2.1, 9.1.7, and 8.19.7.

If we don't want to wait for a release, I can use something like <version> as a placeholder?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried this on 9.1.6 and it seems to enforce a pgp check against a file which is on a wrong path.

Error: Failed trigger upgrade of daemon: failed verification of agent binary: could not get .asc file: fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-9.1.6-f7a485/downloads/elastic-agent-9.2.0-linux-arm64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-9.1.6-f7a485/downloads/elastic-agent-9.2.0-linux-arm64.tar.gz.asc: no such file or directory

Co-authored-by: Colleen McGinnis <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches docs skip-changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants