Implement podman rename via re-apply of containers
To w/a the missing a container rename feature of podman, implement
renaming via removing of the original container and re-applying it from
the same configs but using the new name.
This fixes idempotency issues when service containers are executed
under ephemeral names created via the paunch's unique containers names
generator, while it is expected to have them executed under its wanted
config names.
Reviewed: https:/ /review. openstack. org/621607 /git.openstack. org/cgit/ openstack/ paunch/ commit/ ?id=510f0913539 e92d2e874ae97ef e0606fd277ad4b
Committed: https:/
Submitter: Zuul
Branch: master
commit 510f0913539e92d 2e874ae97efe060 6fd277ad4b
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Dec 3 16:23:32 2018 +0100
Implement podman rename via re-apply of containers
To w/a the missing a container rename feature of podman, implement
renaming via removing of the original container and re-applying it from
the same configs but using the new name.
This fixes idempotency issues when service containers are executed
under ephemeral names created via the paunch's unique containers names
generator, while it is expected to have them executed under its wanted
config names.
Change-Id: If851604d25b6c7 982d950bb9e13dc eada3bfc161
Closes-Bug: #1805410
Signed-off-by: Bogdan Dobrelya <email address hidden>