f369fdd334
Socat as configured would exit on client disconnect. Since there was no active process monitoring, the process would (a) become a zombie, and (b) would not restart, which would disable console access. This commits adds the fork,max-children=1 parametesr to the socat call, which makes socat persistent until it is explicitly killed. Change-Id: I612cd9bca403b7a77ad3e671c1fdadd55353d5f7 Story: 2005024 Task: 29503
10 lines
521 B
YAML
10 lines
521 B
YAML
---
|
|
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.
|