[Fleet]: Dual or incorrect status is shown on performing actions on offline or unhealthy agents.

[amolnater-qasource]

Kibana version: 8.5 BC1 Kibana cloud environment

Host OS: All

Build details:
VERSION: 8.5 BC1
BUILD: 56595
COMMIT: 0d8de4d

Preconditions:

1. 8.5 BC1 Kibana cloud environment should be available.
2. Few agents should be available with various status say: Healthy, Unhealthy and Offline

Steps to reproduce:

1. Install an agent and observe agent in Updating state.
2. Immediately shutdown the agent VM and observe now agent is in dual state: Updating and Offline under Agent details page.
3. For another agent in offline state, click unenroll agent button and observe now agent is in dual state: Updating and Offline under Agent details page.
4. For Unhealthy agent assign it to new policy with other Healthy agents.
5. Observe Healthy agents in Updating state and Unhealthy agents remained in the same state.

Expected Result:
Correct status Updating should be shown on performing actions on offline or unhealthy agents.

Screen Recording:
If agent VM went offline while getting enrolled:

1.mp4

On Unenrolling offline agent:

2.mp4

On Assigning Unhealthy agent to new Policy:

3.mp4

What's working fine:

• Working fine for Healthy status.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[jlind23]

Related to an old version, closing

[amolnater-qasource]

Hi Team,
We have revalidated this issue on latest 8.8.0 SNAPSHOT and found it still reproducible.

Observations:

• Dual or incorrect status is shown on performing actions on offline or unhealthy agents.

Build details:
VERSION: 8.8.0-SNAPSHOT
BUILD: 61970
COMMIT: 5d5e5d3

Screen Recording:

• Unenrolling offline agent:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2023-04-05.10-24-52.mp4

Hence we are re-opening this issue.

Thanks

[juliaElastic]

The dual status was introduced here, so that is expected: #140621

@amolnater-qasource What do you consider incorrect status?

[amolnater-qasource]

Hi @juliaElastic

Thank you for confirming the dual status.

Further, for incorrect status:

• If we trigger unenroll for an offline agent, what should be the status of the agent?
  Currently it shows offline under Agents tab and under Agent details page it shows both Offline and Updating.

In this case, Agent will not get unenrolled without force unenrolling as the agent is offline.
However user might not be able to see it stuck in updating state under Agents tab.

So as per our understanding, on triggering unenroll for an offline agent, status of the agent should update to the Updating state which is the latest state of the agent.
User gets to see the agent stuck in updating for long and then user can force unenroll the stuck agent.

However, as per information under #140621 the priority for Offline agent is higher than Unhealthy or Updating states, so we can close this issue.

Please let us know if we are missing anything.
Thanks!

[juliaElastic]

I think we can close this as expected and change later if we get feedback from users. cc @nchaulet @kpollich

[amolnater-qasource]

Sure Thank you for the update.

We are closing this issue for now.

Thanks!