Paunch does docker/podman rm -f, when removes containers. It seems it
returns too early, having some leftovers (like docker service
endpoints) behind or pending for it to be removed later, in case of
big fat deamons.
Long story short, don't do rm -f and allow it to do its job gracefully
and without a hurry.
Reviewed: https:/ /review. opendev. org/704672 /git.openstack. org/cgit/ openstack/ paunch/ commit/ ?id=de167397958 5e971fbb8d38eba 1d8308f9bbdd92
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit de1673979585e97 1fbb8d38eba1d83 08f9bbdd92
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Jan 16 16:41:59 2020 +0100
Do not force remove containers
Paunch does docker/podman rm -f, when removes containers. It seems it
returns too early, having some leftovers (like docker service
endpoints) behind or pending for it to be removed later, in case of
big fat deamons.
Long story short, don't do rm -f and allow it to do its job gracefully
and without a hurry.
Conflicts:
paunch/ runner. py
paunch/ tests/test_ builder_ compose1. py
paunch/ tests/test_ runner. py
Change-Id: I346c49cb204f27 3bd7077ca515341 2cda9846534 248f7c450d707a1 3c33f19fc3) f5761a26de86a0e c3a2e5bd0f) e4e36bf2084043e 211ca80ecb)
Closes-Bug: #1860004
Co-authored-by: Sergii Golovatiuk <email address hidden>
Signed-off-by: Bogdan Dobrelya <email address hidden>
(cherry picked from commit 3813fc7f2bd5768
(cherry picked from commit d56765a0aff2f8c
(cherry picked from commit 7a002698561ee65