Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security Solution]Inconsistent: Update available banner not removing even after pre-built rules installation #139095

Closed
ghost opened this issue Aug 18, 2022 · 8 comments · Fixed by #139287
Assignees
Labels
8.5 candidate bug Fixes for quality problems that affect the customer experience Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area fixed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.4.1 v8.5.0

Comments

@ghost
Copy link

ghost commented Aug 18, 2022

Related to: #138876

Describe the bug
Inconsistent: Update available banner not removing even after pre-built rules installation

Build Details:

VERSION: 8.4.0 BC5
BUILD: 55374
COMMIT: f12954223a8ad66bbbf77becc4f0557ffd1c92c3

Steps

  • Go to kibana > Alert pages and then click on manage rules
  • observe the banner of update available for elastic prebuilt rules or timeline templates
  • click on update 626 elastic prebuilt rules button
  • Observed the the banner didn't removed even though all rules got installed , performed the hard refresh and even opened in private windows

Screen-Shoot/Cast:

image

10.0.5.177.-.Remote.Desktop.Connection.2022-08-18.17-44-31.mp4
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Aug 18, 2022
@elasticmachine
Copy link
Contributor

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

@ghost ghost added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Aug 18, 2022
@ghost ghost assigned ghost and banderror and unassigned ghost Aug 18, 2022
@ghost ghost added the v8.4.0 label Aug 18, 2022
@banderror
Copy link
Contributor

Oh, I think this one is likely the same (caused by the same reason) as #138876 that we found with @jpdjere earlier this week. Thank you @karanbirsingh-qasource, I will add both to our board and prioritize them to be fixed in 8.4.1.

@banderror banderror added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Detections and Resp Security Detection Response Team Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area 8.5 candidate v8.5.0 and removed triage_needed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. v8.4.0 labels Aug 18, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@banderror
Copy link
Contributor

@karanbirsingh-qasource Dmitrii fixed this bug in #139287. The fix targets the emergency 8.4.1 release that is taking place Tuesday Aug 30.

@ghost
Copy link
Author

ghost commented Aug 26, 2022

Hi @banderror

we have validated this issue on 8.4.1 self managed and found the issue to be still occuring.

Build Details:

Version:8.4.1 BC1
BUILD: 55431
COMMIT: 711ff3a47dba341abd65a2f9814dea5730472bb7

Screen-Cast:
prebuilt.zip

@xcrzx
Copy link
Contributor

xcrzx commented Aug 26, 2022

@karanbirsingh-qasource The fix didn't make it to BC1. Please revalidate the issue once 8.4.1 BC2 is available.

@ghost
Copy link
Author

ghost commented Aug 29, 2022

Hi @xcrzx

we have validated this issue on 8.4.1 BC2 and found the issue to be fixed ✔️

Build Details:
VERSION: 8.4.1-BC2
BUILD: 55434
COMMIT: 415cecc

Screen-Cast:

Rules.-.Kibana.Mozilla.Firefox.2022-08-29.18-28-52.mp4
Alerts.-.Kibana.Mozilla.Firefox.2022-08-29.18-28-17.mp4

Hence we are closing this issue and adding "QA:Validated" tag to it.

thanks !!

@ghost ghost closed this as completed Aug 29, 2022
@ghost
Copy link
Author

ghost commented Sep 23, 2022

Hi Team,

we have re validated this issue on 8.5.0 BC1 and found the issue to still fixed ✔️ .

Build Details:

Version:8.5.0
Commit:0d8de4df69f8084a94cdd9638d7de510813cb5ce
Build:56595

Screen-Shoot

image

Hence we are closing this issue and adding "QA:Validated" tag to it.

thanks !!

@ghost ghost added the QA:Validated Issue has been validated by QA label Sep 23, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.5 candidate bug Fixes for quality problems that affect the customer experience Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area fixed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.4.1 v8.5.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants