github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-06-27 18:51:07 -04:00
Code Issues Projects Releases Packages Wiki Activity

[Docs][9.0.x] Add known issue about AI Obs Assistant getting stuck when attempting to call the call the execute_connector function (#221834)

Browse source 
## Summary

Contributes to https://github.com/elastic/docs-content/issues/1508 by
updating the Kibana 9.0.x release notes to include a known issue about
AI Observability Assistant getting stuck when attempting to call the
`execute_connector` function.

**NOTE:** I also removed the version title on the known issues page
since we're no longer separating known issues by version in the V3
release notes. To convey the affected versions, I added the `Applies
to:` section to all known issue summaries. Example
[here](https://github.com/elastic/kibana/pull/221834/files#diff-30afc7e6ff1580c73ef66adaddc840df18c2c28b7b9b4835cdf8104d3fd2b31cR22).

**Corresponding PRs**
- Kibana 8.18.x known issues:
https://github.com/elastic/kibana/pull/221804

## Preview
- [Known
issues](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/221834/release-notes/known-issues)
This commit is contained in:
Nastasha Solomon 2025-05-28 16:44:28 -04:00 • committed by GitHub
parent 0f2bee8825
commit 95609f9bf6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 19 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/release-notes/known-issues.md
View file

@ -4,11 +4,23 @@ navigation_title: "Known issues"
# Kibana known issues
## 9.0.0
::::{dropdown} Observability AI assistant gets stuck in a loop when attempting to call the `execute_connector` function
:name:known-issue-1508
Applies to: {{stack}} 9.0.0, 9.0.1, 9.0.2
**Details**
The Observability AI assistant gets stuck in a loop when calling the `execute_connector` function. Instead of completing queries, it times out with the error message `Failed to parse function call arguments when converting messages for inference: SyntaxError: Unexpected non-whitespace character after JSON at position 72 and Error: Tool call arguments for execute_connector (...) were invalid`.
::::
::::{dropdown} Observability AI assistant Knowledge Base entries with empty text can lead to Kibana OOM or restarts
:name:known-issue-220339
Applies to: {{stack}} 9.0.0
**Details**
The semantic text migration can cause excessive traffic to a cluster and might eventually cause the Kibana instance to crash due to OOM, together with increase of requests to Elasticsearch & ML nodes.
@ -64,6 +76,8 @@ For more information, check:
::::{dropdown} Issue with follower indices during upgrade
:name: ua-follower-indices
Applies to: {{stack}} 9.0.0
**Details**
In Upgrade Assistant, follower indices may be identified to be reindexed. However, this is not a valid migration path and will result in an error. Instead, the recommendation is to mark as read-only and unfollow the leader index. Cross-cluster replication on that index will not be possible.
@ -75,6 +89,8 @@ Find additional information in the [upgrade documentation](docs-content://deploy
::::{dropdown} Unexpected deprecation warnings for APM indices during upgrade
:name: known-issue-apm-upgrade-on-ech
Applies to: {{stack}} 9.0.0
**Details**
When upgrading an {{ech}} deployment to {{stack}} 9.0.0, you may see deprecation warnings for APM indices, even if you are not using APM.
@ -90,6 +106,8 @@ To proceed with the upgrade to 9.0.0, you must resolve all deprecation notices f
::::{dropdown} Upgrade Assistant - Rollup jobs need to be stopped before rollup indices are reindexed
:name: known-issue-211850
Applies to: {{stack}} 9.0.0
**Details**
Rollup indices, like all indices, created in 7.x or earlier need to be reindexed in preparation for migration to 9.0. However, in addition to the normal reindex process the rollup job also needs to be accounted for.