We would probably like to forward signals only to the direct child
which in turn takes care its children and not to all worker child
processes.
(cherry picked from commit 6258a920fdf8432f39696815765f3320afe92fca)
This change also includes a cherry pick of a fix for bifrost:
Clear ENTRYPOINT configuration for Bifrost
Bifrost was broken by the recent kolla change [1] to use an ENTRYPOINT
for dumb-init. The container failed to start because dumb-init was
trying to run /sbin/init, which expects to be pid 1.
[1] Id91ebb8b0ecc43946845de386350af0536dd661f
(cherry picked from commit b06d8387f50ac9c536941ffddb00c5bdb45753b6)
Reviewed: https:/ /review. openstack. org/621709 /git.openstack. org/cgit/ openstack/ kolla/commit/ ?id=1dacd1944e2 85ef70f60c7e998 2fa2ab180b144e
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 1dacd1944e285ef 70f60c7e9982fa2 ab180b144e
Author: Rabi Mishra <email address hidden>
Date: Wed Oct 24 11:24:07 2018 +0530
Use dumb-init with --single-child
We would probably like to forward signals only to the direct child
which in turn takes care its children and not to all worker child
processes.
(cherry picked from commit 6258a920fdf8432 f39696815765f33 20afe92fca)
This change also includes a cherry pick of a fix for bifrost:
Clear ENTRYPOINT configuration for Bifrost
Bifrost was broken by the recent kolla change [1] to use an ENTRYPOINT
for dumb-init. The container failed to start because dumb-init was
trying to run /sbin/init, which expects to be pid 1.
[1] Id91ebb8b0ecc43 946845de386350a f0536dd661f
(cherry picked from commit b06d8387f50ac9c 536941ffddb00c5 bdb45753b6)
Change-Id: Id91ebb8b0ecc43 946845de386350a f0536dd661f /review. openstack. org/621871/
Depends-On: https:/
Closes-Bug: #1808326
Related-Bug: #1799642
Related-Bug: #1799642