Invalid api key error is observed in CLI on running uninstall command for unenrolled agent.

[amolnater-qasource]

Kibana Build details:

VERSION: 9.0.0 beta1 BC1
BUILD: 83348
COMMIT: fd1f8b62137f14e93716e298e4e931b576e2ca13

Preconditions:

1. 9.0.0 beta BC1 Kibana cloud environment should be available.
2. A few agents should be installed.

Steps to reproduce:

1. Navigate to Fleet>Agents tab.
2. Unenroll the agent from UI.
3. Run agent uninstall command: sudo elastic-agent uninstall
4. Observe invalid api key error on running uninstall command.

NOTE:

• Agent is uninstalled successfully.

Expected Result:
Invalid api key error should not be displayed in CLI on running uninstall command for unenrolled agent.

Screenshot:

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[amolnater-qasource]

@muskangulati-qasource Please review.

[muskangulati-qasource]

Secondary review is Done for this ticket!

[pierrehilbert]

Hey folks,
Are you able to reproduce the same issue for 8.x versions?
Could you please confirm the agent is still getting uninstalled even with this error?

[amolnater-qasource]

Hi @pierrehilbert

Thank you for looking into this issue.
Yes the issue is also reproducible on 8.16.1 agent.

• If the agent is unenrolled from the UI, and then uninstalled, we observe this Invalid api key error.

Screenshot:

Could you please confirm the agent is still getting uninstalled even with this error?

Yes, the agent gets uninstalled even with this error.

Please let us know if anything else is required from our end.
Thanks!!

[cmacknz]

Yes if agent was unenrolled from Fleet, agent's attempt at an uninstall notification will fail.

We should probably modify this error to indicate it isn't a problem if agent was already unenrolled, perhaps we need to special case the invalid api key error in this case. CC @michel-laterman

[pierrehilbert]

Thanks @amolnater-qasource for the additional information.
Glad to read this is not something new and to see that @michel-laterman is already having a PR that will make the error clearer.