Comment 6 for bug 1765802

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-common (stable/pike)

Reviewed: https://review.openstack.org/565552
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=1db5b7421eb87d6d5c5d2490212ac1cab0bb28de
Submitter: Zuul
Branch: stable/pike

commit 1db5b7421eb87d6d5c5d2490212ac1cab0bb28de
Author: Alex Schultz <email address hidden>
Date: Fri Apr 20 16:06:16 2018 -0600

    Add in a STOPSIGNAL configuration

    For docker 1.13.1, if STOPSIGNAL is not provided in the docker image,
    the container will not automatically restart the container. It might be
    better to define this in the Kolla scripts as a configuration option for
    each container, but I'm unsure if it's a problem for any other version
    so it might be best to configure this in tripleo until a newer version
    of docker is consumed. Additionally I'm not sure if any of the
    containers would need something other than STOPSIGNAL SIGTERM which
    should be the default if none is provided.

    Change-Id: I1939f9e6b2c432a672c7426ddabdcfca6ce150b7
    Related-Bug: #1765802
    (cherry picked from commit 039dbccb5d568953e281a21854916b60ad0a98e4)