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

[Fleet] Unenroll action is stuck in progress after force unenroll agent #140794

Closed
juliaElastic opened this issue Sep 15, 2022 · 2 comments · Fixed by #141208
Closed

[Fleet] Unenroll action is stuck in progress after force unenroll agent #140794

juliaElastic opened this issue Sep 15, 2022 · 2 comments · Fixed by #141208
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@juliaElastic
Copy link
Contributor

juliaElastic commented Sep 15, 2022

Related to #140267
There is a bug of unenroll action stuck in "in progress" state after force unenrolling the same agents.
Should we clean somehow the unenroll action when the user force unenroll an agent?

Here I unenrolled an offline agent, then force unenrolled and the UI is stuck with "In progress" status:
Screen Shot 2022-09-14 at 4 54 57 PM

As a solution, the force unenroll logic could check if there is a pending unenroll action for the same agent(s), and write the action results to ES, so that the action would move to completed status in Agent activity.

Originally posted by @nchaulet in #140510 (comment)

@juliaElastic juliaElastic added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team labels Sep 15, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@kpollich
Copy link
Member

As a solution, the force unenroll logic could check if there is a pending unenroll action for the same agent(s), and write the action results to ES, so that the action would move to completed status in Agent activity.

This sounds like a viable path forward to me. The "force" nature of this action seems to me like it'd be okay for us to make manual edits to the action status throughout the process. I'm +1 on this approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants