Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Fleet] Fleet server standalone coordination is not working #2605

Closed
nchaulet opened this issue May 18, 2023 · 0 comments · Fixed by #2606
Closed

[Fleet] Fleet server standalone coordination is not working #2605

nchaulet opened this issue May 18, 2023 · 0 comments · Fixed by #2606
Assignees
@nchaulet
Labels
Team:Fleet Label for the Fleet team

Comments

@nchaulet
Copy link
Member

nchaulet commented May 18, 2023 •
edited
Loading

Description

When running fleet server standalone it seems the coordinator is not working

It seems it because we need an agent ID https://github.com/elastic/fleet-server/blob/main/internal/pkg/coordinator/monitor.go#L103-L108

Potential solution

It probably make sense to generate an agent ID in standalone @michel-laterman @jsoriano what do you think? I created a PR that explore that solution and it seems to work #2606
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nchaulet nchaulet

Labels
Team:Fleet Label for the Fleet team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Fleet] Fake agent in fleet server standalone elastic/fleet-server
1 participant
@nchaulet