Containers left in an incomplete status are not recovered

Bug #1955056 reported by Takashi Kajinami
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Takashi Kajinami

Bug Description

# This issue was initially reported in

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.

Revision history for this message
Takashi Kajinami (kajinamit) wrote :

The fix was proposed to stable/ussuri:

Changed in paunch:
status: New → In Progress
assignee: nobody → Takashi Kajinami (kajinamit)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/paunch ussuri-eol

This issue was fixed in the openstack/paunch ussuri-eol release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.