Skip to content

Propogate 503 errors from elasticsearch inside of Fleet Server back to the client #5197

Description

@blakerouse

Describe the issue:

At the moment when a 503 error occurs during enrollment with an Elastic Agent to Fleet Server that shows as a 500 error back to the Elastic Agent. This is causes the Elastic Agent to not handle the retries, and then enrollment just fails.

Describe a specific use case for the issue:

There are many cases where elasticsearch can be temporarily unhealthy which then causes Fleet Server to be unhealthy. It is good to let the caller know this and most likely a retry will cause it to succeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions