[Security Solution] The status of isolate and release keeps on showing pending even though it is successful

[muskangulati-qasource]

Description:
The status of isolate and release keeps on showing pending even though it is successful

Build Details:

Kibana version: 8.0.0 rc2
Build: 49092
Commit: 93d9bd54452711c449fe07e4f23c43a4a0e519c3
Artifact page: https://staging.elastic.co/8.0.0-rc2-c0b0e70d/summary-8.0.0-rc2.html

Browser Details:
All

Preconditions:

1. Kibana user should be logged in.

Steps to Reproduce:

1. Isolate an endpoint and observe the status keeps on showing as pending.

Impacted Test case:
N/A

Actual Result:
The status of isolate and release keeps on showing pending even though it is successful

Expected Result:
The status of isolate and release should be updated and not shown as pending once it is successful

What's working:
N/A

What's not working:
N/A

Screen Recording:

IsolateRelease.mp4

Logs:
N/A

[elasticmachine]

Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[muskangulati-qasource]

@manishgupta-qasource please review!!

[manishgupta-qasource]

Reviewed & assigned to @kevinlog

[kevinlog]

@muskangulati-qasource - I noticed in your video that the Endpoint never sends the "Completed" notification in the actions log.

Can you verify that your VMs are actually completing the isolation action? You can go to the VM and find the desktop notification or try to connect to some website and it should be isolated.

I just verified this on an rc2 build myself and I'm seeing it be successful, see the below:

You can see that the Endpoint is sending back the success messages in the Activity log.

cc\ @ferullo @ashokaditya

[kevinlog]

@muskangulati-qasource @ashokaditya I know what the problem is. If the namespace is different, then we need to expand the query to go beyond just .logs-actions-response-default. I'm raising this to critical so that we can merge it in before the last 8.0 BC

[ashokaditya]

PR /pull/123741

[kevinlog]

@muskangulati-qasource the fix for this is merged and will be available in the next 8.0 build candidate. Since I raised this as a blocker for 8.0, I'm going to close this ticket communicate to the release team that the fix is merged and the BC can be built.

I'm adding the "Ready for Test" label. After it's tested, you can remove that label and leave a comment as usual. Thanks!

[muskangulati-qasource]

Hi @kevinlog,

We tested this ticket & found that the issue is Fixed on the 8.0.0 RC2 -BC4 build. Please find below the testing details:

Build Details:

Kibana Version: 8.0.0 RC2 BC4
Build: 49192
Commit: 57ca5e139a33dd2eed927ce98d8231a1f217cd15
Artifacts link: https://staging.elastic.co/8.0.0-rc2-27a50a27/summary-8.0.0-rc2.html

Screenshots:

Hence, closing this ticket and marking it as "Validated".

Thanks!

[harshitgupta-qasource]

Bug Conversion

• Test-Case updated:
  • https://elastic.testrail.io/index.php?/cases/view/149908

Thanks!