[Fleet]: Agents tab gets crashed on clicking Agent activity for user role with Agents: Read and other Sub Features: None.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.16.0-SNAPSHOT
BUILD: 77679
COMMIT: 6b091fe3b410eaae9d4805c0a3c0ea6168bf66b0

Role:

Integrations: All
Fleet: All
Agents: Read
Agent policies: None
Settings: None

Preconditions:

1. 8.16.0-SNAPSHOT Kibana cloud environment should be available.
2. New User should be created with above defined role.

Steps to reproduce:

1. Login with the above user.
2. Navigate to Agents tab and click Agent activity.
3. Request for Agent diagnostics again and again, to get Review error logs badge.
4. Observe Agents tab crashes, and error logs are displayed.

Logs:
logs.txt

Expected Result:
Agents tab shouldn't get crashed on clicking Agent activity for user role with Agents: Read and other Sub features: None.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-08-27.13-57-02.mp4

Feature:
https://github.com/elastic/ingest-dev/issues/2903

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@karanbirsingh-qasource Please review.

[ghost]

secondary review of this ticket is done

[amolnater-qasource]

Hi Team,

Just an update that the issue is also reproducible for Superuser with all privileges enabled.

Thanks!
JFI @juliaElastic

[jen-huang]

Hi, the fix will be merged in #191671. This should rather be revalidated while testing #189861, because the cause of the issue comes from this new type of action (automatic unenrollment).

[amolnater-qasource]

Hi Team,

We have revalidated this issue on latest 8.16.0 SNAPSHOT kibana cloud environment and found it fixed now.

Observations:

• Agents tab doesn't gets crashed on clicking Agent activity for custom user and for superuser.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-09-13.10-40-52.mp4

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-09-13.10-39-02.mp4

Build details:
VERSION: 8.16.0 SNAPSHOT
BUILD: 78101
COMMIT: f51481d

Hence, we are marking this issue as QA:Validated.

Thanks!