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

Add known issue with offline agents failing to unenroll from Fleet #2392

Merged
merged 1 commit into from
Nov 22, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,43 @@ This issue will be resolved in version 8.5.2. We advise Windows users not to
upgrade to version 8.5.1.
====

[[known-issue-2383]]
.Offline {agent}s fail to unenroll after timeout has expired
[%collapsible]
====

*Details*

A {fleet-server-issue}/2091[known issue] in {fleet-server} 8.5.1 prevents
offline agents from being automatically unenrolled after the unenrollment
timeout expires.

*Impact* +

Offline agents will be displayed in the {fleet} Agents list until you explicitly
force <<unenroll-elastic-agent,unenroll>> them. You can do this through the
{fleet} UI or by using the API.

To use the API:

. Find agent's ID. Go to *{fleet} > Agents* and click the agent to see its
details. Copy the Agent ID.

. In a terminal window, run:
+
[source,shell]
----
curl -u <username>:<password> --request POST \
--url <kibana_url>/api/fleet/agents/<agentID>/unenroll \
--header 'content-type: application/json' \
--header 'kbn-xsrf: xx' \
--data-raw '{"force":true,"revoke":true}' \
--compressed
----
+
Where `<agentID>` is the ID you copied in the previous step.

====

[discrete]
[[enhancements-8.5.1]]
Expand Down