-
Notifications
You must be signed in to change notification settings - Fork 148
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
[8.10](backport #3415) elastic-agent install
: Only uninstall when Agent is installed
#3472
Conversation
🌐 Coverage report
|
Several integration tests failed in Buildkite with errors like this one:
Maybe some previous test didn't finish cleanup? Re-running the Buildkite build to see if this is a transient error... |
The build is failing again with the same errors as before: #3472 (comment).
This makes me think there's some PR fixing the testing framework's fixture uninstallation code that probably hasn't been backported to the |
@ycombinator I can't think of any recent PRs that could have affected this behavior. We still rely on the fixture for uninstalling at the end of a test. I am wondering if in some of our testcases we don't detect the agent as "installed" and with this change we have some stuff that is left over... |
Thanks @pchila. Just strange that we're only seeing this on |
f025104
to
f02a34c
Compare
This pull request has not been merged yet. Could you please review and merge it @ycombinator? 🙏 |
I'm going to revisit this PR once #3495 is merged. |
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
This pull request has not been merged yet. Could you please review and merge it @ycombinator? 🙏 |
* Only uninstall if --force is present * Improve help text * Add missing newline * Don't pass force * Fix more conflicts * Fixing compile error introduced while resolving conflicts (cherry picked from commit 0c43005) # Conflicts: # internal/pkg/agent/install/install.go
f02a34c
to
0195a27
Compare
This is an automatic backport of pull request #3415 done by Mergify.
Cherry-pick of 0c43005 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com