-
Notifications
You must be signed in to change notification settings - Fork 143
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
Enrolling into Fleet can fail because the control socket doesn't exist #3664
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
A solution to this was started in #3631, but changing the agent to wait longer for this error broke enrollment in a Docker container. |
@cmacknz I'm a bit confused by this issue.
Should I add back #3554 and then fix the enrol process? |
You can bring back #3628 as a starting point but enrolling a Docker container into Fleet needs to be fixed before the change can be merged.
|
This is frequently affecting our integration tests because we are frequently enrolling as part of the agent installation. A typical failure looks like:
elastic-agent-control.sock
file doesn't exist yet. Possibly we just need to retry accessing it, but there could have been an unlogged problem creating it.Successfully enrolled the Elastic Agent.
which I don't think is expected. The agent is enrolled, but it won't connect to Fleet until it is manually restarted.The text was updated successfully, but these errors were encountered: