-
Notifications
You must be signed in to change notification settings - Fork 82
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
Fix self monitor to report starting waiting on fleet-server input #768
Conversation
…o be added to policy.
This pull request does not have a backport label. Could you fix it @blakerouse? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
…o be added to policy. (#768) (#774) (cherry picked from commit 334cd2d) Co-authored-by: Blake Rouse <[email protected]>
…o be added to policy. (#768) (#773) (cherry picked from commit 334cd2d) Co-authored-by: Blake Rouse <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
What is the problem this PR solves?
This solves the issue where Kibana could create the policy that fleet-server is waiting to exist, but when Kibana creates it, it doesn't add the
fleet-server
input to it. Before fleet-server would report this as an error and would cause the Elastic Agent to keep restarting thefleet-server
constantly.How does this PR solve the problem?
This solves the issue by changing the logic to report the missing input as starting. This will allow the Elastic Agent to keep the
fleet-server
process running (removing the constant restart loop). Elastic Agent will also print the nice message that fleet-server provides back to the user.Once the
fleet-server
input is added to the policy,fleet-server
will notice that it now exists and will continue to normal operation.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues