Add known issues for 'no agent found', Agent uninstall exception #1483
Conversation
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
kilfoyle
changed the title
kilfoyle
changed the title
kilfoyle
changed the title
docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc
Outdated
Show resolved
Hide resolved
| As a workaround you can... | ||
|
|
||
| //* Upgrade your {stack}? | ||
| //* Force uninstall the agent using a command? |
There was a problem hiding this comment.
@blakerouse does retrying the uninstall operation work when this happens?
There was a problem hiding this comment.
For now, so that we can merge this and have customers able to see it, I've changed the "Impact" section to read: We're currently investigating the issue and will update this page when a workaround becomes available.
@blakerouse, @cmacknz Please let me know if the above is okay, and when we have a workaround if you let me know I'll be happy to update this section.
|
👋 I've created a public kb on our support portal, but this one would likely have more audience. |
|
|
||
| This issue prevents {agent} from being uninstalled on Windows systems. | ||
|
|
||
| We're currently investigating the issue and will update this page when a workaround becomes available. |
There was a problem hiding this comment.
Retrying the uninstall again seems like a reasonable work around until we get some evidence it doesn't work, it's not simple to create an agent in this state for me to test.
If that fails, we can post instructions on manually removing the agent service and deleting the files in the installation directory.
There was a problem hiding this comment.
Sounds good. I've changed this to simply "As a workaround, we recommend trying again to uninstall the agent."
docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc
Outdated
Show resolved
Hide resolved
* Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40)
* Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40)
* Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40)
…) (#1517) * Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40) Co-authored-by: David Kilfoyle <[email protected]>
…) (#1516) * Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40) Co-authored-by: David Kilfoyle <[email protected]>
…) (#1515) * Add known issue for 'no agent found' * add agent uninstall issue * Fixup * Add 'Fleet-managed' to second issue * Indicate that workaround is pending * Update workaround * fix Kibana attribute (cherry picked from commit 8b58e40) Co-authored-by: David Kilfoyle <[email protected]>
This adds docs for the known issues:
Closes: #1481
Closes: #1482
I'll update the "Impact" section of the second issue as soon as we have a suggested workaround (Blake or Craig, if you can please let me know once we have that).