Add known issue for PipelineBusv2 to 8.15.x release notes #16661
Conversation
|
@yaauie Can you update the issue name please - the automatic issue namer kicked in with the two commits |
yaauie
changed the title
Co-authored-by: Karen Metts <[email protected]>
There was a problem hiding this comment.
I had added comments that we had double entries for 8.15.1 and no entries for 8.15.2, but it appears that issue got resolved while I was reviewing.
Now it appears that the only change needed is to remove the + but keep the line as indicated inline.
I think we're close, but I'll verify in the preview and then sign off.
| @@ -172,6 +196,14 @@ If this situation occurs, {ls} may fail to start or some plugins may use a malfo | |||
| Check out issue https://github.com/elastic/logstash/issues/16437[#16437] for details. | |||
| + | |||
| Workaround: Downgrade to {ls} 8.15.0, or temporarily avoid using environment and keystore variable references. | |||
| * **{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.** | |||
| Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details. | |||
| + | |||
There was a problem hiding this comment.
I think this one is necessary because it's in a bulleted list?
There was a problem hiding this comment.
I suggested removing the bullet because it was a single item. When the bullet went away, the + needed to go away, too, to avoid it rendering.
There was a problem hiding this comment.
Ideally, the + should go, but the line should remain to force rendering into two distinct paragraphs.
There was a problem hiding this comment.
This is what it looks like now. Not the worst, but not the best.
formatting: - plus-to-continue only in lists, - consistency of linebreaks before next section Co-authored-by: Karen Metts <[email protected]>
|
@logstashmachine backport 8.16 |
Release notes
[rn: skip]
What does this PR do?
Adds release notes for the #16657 known issue in v2 of the pipeline bus which can prevent shutdown.