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

V2: Agent policy change is not applied properly and requires agent restart #996

Closed
aleksmaus opened this issue Aug 24, 2022 · 2 comments · Fixed by #1258
Closed

V2: Agent policy change is not applied properly and requires agent restart #996

aleksmaus opened this issue Aug 24, 2022 · 2 comments · Fixed by #1258
Assignees
Labels
bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.6.0

Comments

@aleksmaus
Copy link
Member

Agent doesn't apply configuration change properly.
Running off of the latest V2 branch:
https://github.com/elastic/elastic-agent/tree/feature-arch-v2

Steps to reproduce:

  1. Enroll the agent from the command line
  2. Run the agent from the command line
  3. Update the policy. In this particular case was playing with osquery_manager configuration. The agent restart is required in order to get the configuration reloaded properly.
@aleksmaus aleksmaus added bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.5.0 labels Aug 24, 2022
@aleksmaus
Copy link
Member Author

So I fixed the shutdown locking in V2 here #1258
retested this issues with these changes and now the configuration updates are applied.
This can be closed once the #1258 is reviewed and merged.

@jlind23 jlind23 linked a pull request Sep 27, 2022 that will close this issue
2 tasks
@aleksmaus
Copy link
Member Author

Closing as the linked PR is merged now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants