From ddde706469cee2c2f0d28e32b4b990b4c3d78cbd Mon Sep 17 00:00:00 2001 From: Eric Fried Date: Fri, 30 Aug 2019 10:00:57 -0500 Subject: [PATCH] Reno for SIGHUP fix Adds a release note for the fix at I8096fc7fd014e6dd299fae8ab073336c7cae362a Change-Id: I4682950ac12f763737489c510246d54aed80b80f Related-Bug: #1715374 --- ...o-restart-client-channel-619545294557bf2b.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 releasenotes/notes/auto-restart-client-channel-619545294557bf2b.yaml diff --git a/releasenotes/notes/auto-restart-client-channel-619545294557bf2b.yaml b/releasenotes/notes/auto-restart-client-channel-619545294557bf2b.yaml new file mode 100644 index 0000000..c68f724 --- /dev/null +++ b/releasenotes/notes/auto-restart-client-channel-619545294557bf2b.yaml @@ -0,0 +1,15 @@ +--- +fixes: + - | + When the privsep helper dies, the client side PrivContext now restarts the + client channel and the helper so that privileged commands can continue to + be processed. See `bug 1715374`_ for details. In conjunction with the fix + for `bug 1794708`_ in oslo.service, the nova-compute service now behaves + correctly when it receives ``SIGHUP``. + + .. note:: This only works for the ``ROOTWRAP`` method of starting the + daemon. With the ``FORK`` method we've dropped privileges and no + longer have the ability to restart the daemon in privileged mode. + + .. _`bug 1715374`: https://bugs.launchpad.net/nova/+bug/1715374 + .. _`bug 1794708`: https://bugs.launchpad.net/oslo.service/+bug/1794708