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

Cherry-pick #23537 to 7.x: [Elastic Agent] Set status Failed if configuration applying fails #23600

Merged
merged 1 commit into from
Jan 21, 2021

Conversation

blakerouse
Copy link
Contributor

Cherry-pick of PR #23537 to 7.x branch. Original message:

What does this PR do?

Adjusted libbeat to report the failure of reloading the configuration as failed.

Why is it important?

Without this the running beat will stay degraded until the next configuration reload. If applying configuration fails then it is really an error and Elastic Agent should kill it and restart the beat (which it will do with this change).

Checklist

  • My code follows the style guidelines of this project
  • [ ] 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

…astic#23537)

* Set status to Failed if configuration applying fails.

* Add changelog.

* Don't cleanup paths on crash, as it will be restart. Fix ownership.

(cherry picked from commit e0881de)
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Team:Ingest Management)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/agent (Team:Agent)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jan 20, 2021
@blakerouse blakerouse self-assigned this Jan 20, 2021
@elasticmachine
Copy link
Collaborator

💚 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

Expand to view the summary

Build stats

  • Build Cause: Pull request #23600 opened

    • Start Time: 2021-01-20T21:20:05.290+0000
  • Duration: 46 min 14 sec

  • Commit: dac706f

Test stats 🧪

Test Results
Failed 0
Passed 5440
Skipped 358
Total 5798

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 5440
Skipped 358
Total 5798

Copy link
Contributor

@michalpristas michalpristas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

backport looks ok

@blakerouse blakerouse merged commit 956b068 into elastic:7.x Jan 21, 2021
@blakerouse blakerouse deleted the backport_23537_7.x branch January 21, 2021 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants