-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #25423 to 7.13: Do not use unversioned home with watcher binary path #25460
Conversation
Pinging @elastic/agent (Team:Agent) |
Pinging @elastic/ingest-management (Team:Ingest Management) |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errorsExpand to view the tests failures
|
Test | Results |
---|---|
Failed | 1 |
Passed | 6739 |
Skipped | 24 |
Total | 6764 |
Genuine test errors
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Build&Test / x-pack/elastic-agent-windows-2012-windows-2012-r2 / TestConfigurableFailed – github.com/elastic/beats/v7/x-pack/elastic-agent/pkg/agent/operation
Cherry-pick of PR #25423 to 7.13 branch. Original message:
What does this PR do?
The problem is when agent tries to invoke watcher which checks upgraded agent for failures and at the same time unversioned home path is set.
Usually agent took its home path which is
{top_path}/data/elastic-agent-{hash}/elastic-agent
and invokedwatch
sub-command on binary at that path.When unversioned path is set it tries to run watcher from
{top_path}/data/elastic-agent
and as so it results in binary not found.Fixes: #25371
Why is it important?
Reduce noise created by failng attempt to run this. This is just a case when running
container
sub-command which tempers paths.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.cc @michel-laterman