[backport 8.3]: Fix Agent failing to run in standalone mode (#501)#504
Merged
aleksmaus merged 1 commit intoelastic:8.3from Jun 2, 2022
Merged
Conversation
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Contributor
🌐 Coverage report
|
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?
Fixes Agent failing to run in standalone mode.
This is a backport of PR #501 to 8.3 branch
Related to the following issue: elastic/cloud-on-k8s#5720
The root cause of the issue here is that Agent when running standalone tries to write the agentID into fleet.enc (which is encrypted former fleet.yml).
If fails because the the encryption seed was not created if the agent was not enrolled.
The fix here is to create the agent secret on run. This will not create the new key if there is one that already exists after enrollment. At it allows the agent to write the agentID into fleet.enc file.
Why is it important?
Fixes Agent failing to run in standalone mode: elastic/cloud-on-k8s#5720
Checklist
How to test this PR locally
Run the agent locally without enrolling it first with fleet.
Related issues
Screenshots
The agent runs in the standalone mode successfully.
