summaryrefslogtreecommitdiff
path: root/releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml')
-rw-r--r--releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml15
1 files changed, 8 insertions, 7 deletions
diff --git a/releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml b/releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml
index 980e0f9da..d02bf9725 100644
--- a/releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml
+++ b/releasenotes/notes/socat-respawn-de9e8805c820a7ac.yaml
@@ -1,9 +1,10 @@
---
fixes:
- - Ironic does not monitor the socat proxy started for serial console
- access. The socat process would exit on client disconnect, which
- would (a) leave a zombie socat process in the process table and (b)
- disable any subsequent serial console connections. Fixed the issue by
- updating Ironic to call socat with the ``fork,max-children=1`` options,
- which makes socat persist and accept multiple connections (but only one
- at a time). See https://storyboard.openstack.org/#!/story/2005024.
+ - Fixes an issue where the socat process would exit on client disconnect,
+ which would (a) leave a zombie socat process in the process table and (b)
+ disable any subsequent serial console connections. This issue was
+ addressed by updating ironic to call socat with the
+ ``fork,max-children=1`` options, which makes socat persist and accept
+ multiple connections (but only one at a time).
+ Please see story `2005024 <https://storyboard.openstack.org/#!/story/2005024>`_
+ for additional information.