After Undercloud upgrade to Podman, neutron-dnsmasq is still running in Docker

[Emilien Macchi]

How to reproduce:

1) deploy an undercloud in Rocky (doc: https://docs.openstack.org/tripleo-docs/latest/install/installation/installation.html#installing-the-undercloud):

 $ openstack undercloud install

2) upgrade your undercloud, (follow this procedure: https://docs.openstack.org/tripleo-docs/latest/upgrade/undercloud.html)

 $ openstack undercloud upgrade

3) You'll see that neutron-dnsmasq containers are still running:

+ docker ps --all --size
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZE
09fcfe14f64f docker.io/tripleorocky/centos-binary-neutron-dhcp-agent:20b34d57f16b908ee3226c6c516269c557c1e946_9ed865e1 "ip netns exec qdh..." 50 minutes ago Up 50 minutes neutron-dnsmasq-qdhcp-12650816-a40d-4886-a020-3c5baf0db8ef 0 B (virtual 1.14 GB)

Seen in CI:
http://logs.openstack.org/05/620405/10/check/tripleo-ci-centos-7-containerized-undercloud-upgrades/2fc256e/logs/undercloud/var/log/extra/docker/docker_allinfo.log.txt.gz

We need to migrate these containers to be run in Podman.

[Adam Ratcliff (adamjr)]

Why is podman popping up in Rocky logs? The Rocky release notes have nothing about podman and I am getting podman pulls in my ansible deployment logs!!!!

Even the stein release notes say Podman is now the default ContainerCli unless you deploy Pacemaker. then you must run Docker when deploying on CentOS7.

[Bogdan Dobrelya (bogdando)]

I'm not sure why do we have any mentions of podman for Rocky, like https://review.opendev.org/#/c/588659/4/container-images/tripleo_kolla_template_overrides.j2