Skip to content

Commit c772393

Browse files
Fixes duplicate version listed in known issue in 9.x Security release notes (#1635)
^ 9.0.1 was incorrectly listed twice in the affected versions field for the first known issue on the page. That field should show that 9.0.0, 9.0.1, and 9.0.2 are affected. Preview: [Elastic Security known issues](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1635/release-notes/elastic-security/known-issues)
1 parent 38704db commit c772393

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

release-notes/elastic-security/known-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Known issues are significant defects or limitations that may impact your impleme
1818

1919
:::{dropdown} The entity risk score feature may stop persisting risk score documents
2020

21-
Applies to: {{stack}} 9.0.1, 9.0.1, 9.0.2
21+
Applies to: {{stack}} 9.0.0, 9.0.1, 9.0.2
2222

2323
On May 30, 2025, it was discovered that the entity risk score feature may stop persisting risk score documents if risk scoring was turned on before you upgraded to {{stack}} 8.18.0+ or 9.0.0+. This is due to a bug that prevents the `entity_analytics_create_eventIngest_from_timestamp-pipeline-<space_name>` ingest pipeline (which is set as a default pipeline for the risk scoring index in {{stack}} 8.18.0) from being created when {{kib}} starts up.
2424

0 commit comments

Comments
 (0)