github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

Adding alerting upgrade known issue for 8.3.0 and 8.3.1 (#135604)

Browse source 
* Adding alerting upgrade known issue for 8.3.0 and 8.3.1

* Incorporating Lisa's feedback, many thanks.

* [DOCS] Add link in known issue

Co-authored-by: lcawl <lcawley@elastic.co>
This commit is contained in:
Brandon Kobel 2022-06-30 15:56:42 -07:00 • committed by GitHub
parent 21f12d1ffc
commit ebe610d846
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 42 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

42
docs/CHANGELOG.asciidoc
View file

@ -35,6 +35,27 @@ Review important information about the {kib} 8.3.x releases.
Review the following information about the {kib} 8.3.1 release.
[float]
[[known-issues-8.3.1]]
=== Known issues
Alerting users who are running 8.2 should not upgrade to either 8.3.0 or 8.3.1.
Both 8.3.0 and 8.3.1 have a bug where alerting rules that were created or edited
in 8.2 will stop running on upgrade. If you have upgraded to 8.3.0 or 8.3.1 and
your alerting rules have stopped running with an error similar to the following
example, you will need to use the *Update API key* operation in
*{stack-manage-app} > {rules-ui}* to restore the alerting rule to a functional
state. It should be noted that the *Update API Key* operation causes the
alerting rule to run as the user that performed the operation. For more details
about API key authorization, refer to <<alerting-authorization>>.
Example error message::
[source,text]
----
<rule-type>:<UUID>: execution failed - security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_security/user/_has_privileges], caused by: ""
----
[float]
[[breaking-changes-8.3.1]]
=== Breaking change
@ -87,6 +108,27 @@ Platform::
Review the following information about the {kib} 8.3.0 release.
[float]
[[known-issues-8.3.0]]
=== Known issues
Alerting users who are running 8.2 should not upgrade to either 8.3.0 or 8.3.1.
Both 8.3.0 and 8.3.1 have a bug where alerting rules that were created or edited
in 8.2 will stop running on upgrade. If you have upgraded to 8.3.0 or 8.3.1 and
your alerting rules have stopped running with an error similar to the following
example, you will need to use the *Update API key* operation in
*{stack-manage-app} > {rules-ui}* to restore the alerting rule to a functional
state. It should be noted that the *Update API Key* operation causes the
alerting rule to run as the user that performed the operation. For more details
about API key authorization, refer to <<alerting-authorization>>.
Example error message::
[source,text]
----
<rule-type>:<UUID>: execution failed - security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_security/user/_has_privileges], caused by: ""
----
[float]
[[breaking-changes-8.3.0]]
=== Breaking change