[8.19] (backport #10217) Fix error logging for provider failures#10381
Merged
straistaru merged 1 commit into8.19from Oct 8, 2025
Merged
[8.19] (backport #10217) Fix error logging for provider failures#10381straistaru merged 1 commit into8.19from
straistaru merged 1 commit into8.19from
Conversation
* Fix error logging for provider failures * Add changelog fragment * Omit nil error detail from logs (cherry picked from commit 0a5c2a4)
mergify
bot
requested review from
michalpristas and
pkoutsovasilis
and removed request for
a team
4 tasks
github-actions
bot
added
bug
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Contributor
💚 Build Succeeded
cc @straistaru |
straistaru
approved these changes
Oct 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Avoid logging a nil error for provider exits.
Why is it important?
Some providers intentionally stop and return a nil error; they already log the exit reason internally. The previous log formatted a nil error into "%!s()", which can be confusing (e.g.
provider "env" failed to run (will retry in 30s): %!s()). This change removes the incorrect formatting and only includes the error text when non-nil.Checklist
[ ] 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./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
None.
Related issues
This is an automatic backport of pull request Fix error logging for provider failures #10217 done by Mergify.