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

[8.5](backport #1285) Expand status reporter/controller interfaces to allow local reporters #1304

Merged
merged 1 commit into from
Sep 26, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 26, 2022

This is an automatic backport of pull request #1285 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…#1285)

* Expand status reporter/controller interfaces to allow local reporters

Add a local reporter map to the status controller. These reporters are
not used when updating status with fleet-server, they are only used to
gather local state information - specifically if the agent is degraded
because checkin with fleet-server has failed. This bypasses the bug that
was introduced with the liveness endpoint where the agent could checkin
(to fleet-server) with a degraded status because a previous checkin
failed. Local reporters are used to generate a separate status. This
status is used in the liveness endpoint.

* fix linter

(cherry picked from commit 717708a)
@mergify mergify bot requested a review from a team as a code owner September 26, 2022 17:23
@mergify mergify bot added the backport label Sep 26, 2022
@mergify mergify bot requested review from AndersonQ and michel-laterman and removed request for a team September 26, 2022 17:23
@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: 2022-09-26T17:23:42.169+0000

  • Duration: 18 min 34 sec

Test stats 🧪

Test Results
Failed 0
Passed 4955
Skipped 17
Total 4972

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages.

  • run integration tests : Run the Elastic Agent Integration tests.

  • run end-to-end tests : Generate the packages and run the E2E Tests.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Contributor

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 97.333% (73/75) 👍
Files 67.797% (160/236) 👍
Classes 68.182% (315/462) 👍
Methods 52.417% (889/1696) 👎 -0.062
Lines 38.735% (9575/24719) 👎 -0.072
Conditionals 100.0% (0/0) 💚

@michel-laterman michel-laterman merged commit b168e8e into 8.5 Sep 26, 2022
@michel-laterman michel-laterman deleted the mergify/bp/8.5/pr-1285 branch September 26, 2022 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants