+++ This bug was initially created as a clone of Bug #2032139 +++ Description of problem: Currently paunch looks for the existing container and compare image id and CONFIG_HASH (and some additional environments if needed) to determine whether it should recreate the container. When deployment times out while starting containers, paunch can leave containers in an incomplete status as described below. - The container was recreated, registered to systemd, but was not enabled/started - The container was recreated, registered to systemd, enabled, but was started - The container was recreated, but was not registered to systemd. In such situation paunch can't detect these incomplete containers and next deployment successfully runs without any errors, leaving these containers without any fix. We should ensure paunch registers systemd service and starts these containers properly. Version-Release number of selected component (if applicable): python3-paunch-5.3.3-1.20210412123423 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.4), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8794