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.

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

Merged
merged 1 commit into from
Oct 11, 2021

Conversation

blakerouse
Copy link
Contributor

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 the fleet-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 commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@blakerouse blakerouse added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Oct 11, 2021
@blakerouse blakerouse self-assigned this Oct 11, 2021
@mergify
Copy link
Contributor

mergify bot commented Oct 11, 2021

This pull request does not have a backport label. Could you fix it @blakerouse? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • v/d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Oct 11, 2021
@blakerouse blakerouse added the backport-v7.16.0 Automated backport with mergify label Oct 11, 2021
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-11T13:58:43.104+0000

  • Duration: 13 min 27 sec

  • Commit: b8f6877

Test stats 🧪

Test Results
Failed 0
Passed 221
Skipped 0
Total 221

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@blakerouse blakerouse merged commit 334cd2d into elastic:master Oct 11, 2021
@blakerouse blakerouse deleted the fix-763 branch October 11, 2021 18:07
mergify bot pushed a commit that referenced this pull request Oct 11, 2021
…o be added to policy. (#768)

(cherry picked from commit 334cd2d)
@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Oct 11, 2021
@blakerouse blakerouse added backport-skip Skip notification from the automated backport with mergify backport-v7.15.0 Automated backport with mergify v7.15.0 and removed backport-skip Skip notification from the automated backport with mergify labels Oct 11, 2021
mergify bot pushed a commit that referenced this pull request Oct 11, 2021
…o be added to policy. (#768)

(cherry picked from commit 334cd2d)
mergify bot added a commit that referenced this pull request Oct 11, 2021
…o be added to policy. (#768) (#774)

(cherry picked from commit 334cd2d)

Co-authored-by: Blake Rouse <[email protected]>
mergify bot added a commit that referenced this pull request Oct 11, 2021
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v7.15.0 Automated backport with mergify backport-v7.16.0 Automated backport with mergify Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v7.15.0 v7.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fleet Server exits if policy does not have fleet-server package
3 participants