Paunch ignores Created containers while it must start them

Bug #1891285 reported by Bogdan Dobrelya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Medium
Unassigned

Bug Description

[zuul@standalone ~]$ sudo paunch apply --debug --file /var/lib/tripleo-config/container-startup-config/step_4/placement_api.json --config-id tripleo_step4
Paunch is deprecated and has been replaced by tripleo_container_manage role in tripleo-ansible.
...
$ podman inspect --type container --format {{index .Config.Labels "config_data"}} placement_api
...
Running container: placement_api
Skipping existing container: placement_api

[zuul@standalone ~]$ sudo podman ps -a | grep place
903fc5df35f2 192.168.24.1:8787/tripleomaster/centos-binary-placement-api:current-tripleo-updated-20200526113651 kolla_start 41 seconds ago Created placement_api

Changed in tripleo:
milestone: none → victoria-3
tags: added: train-backport-potential ussuri-backport-potential
tags: added: queens-backport-potential
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
Changed in tripleo:
milestone: victoria-3 → wallaby-1
Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Changed in tripleo:
milestone: wallaby-3 → wallaby-rc1
Changed in tripleo:
milestone: wallaby-rc1 → xena-1
Changed in tripleo:
milestone: xena-1 → xena-2
Changed in tripleo:
milestone: xena-2 → xena-3
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.