commit 70f3a398fdac299a78c39f389fa1dab91c36c55d
Author: Will Szumski <email address hidden>
Date: Wed Feb 21 16:14:19 2024 +0000
Move podman socket activation to podman role
The expectation was that the podman role would fully configure the
podman service, but we needed to run the podman_sdk role for socket
activation to be enabled.
It also meant that you needed to run the podman_sdk role after the
podman role (as it expected that podman was already installed) which is
not always desirable. For instance, in kayobe, we setup the virtualenv
before configuring the container engine.
Reviewed: https:/ /review. opendev. org/c/openstack /ansible- collection- kolla/+ /909692 /opendev. org/openstack/ ansible- collection- kolla/commit/ 70f3a398fdac299 a78c39f389fa1da b91c36c55d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 70f3a398fdac299 a78c39f389fa1da b91c36c55d
Author: Will Szumski <email address hidden>
Date: Wed Feb 21 16:14:19 2024 +0000
Move podman socket activation to podman role
The expectation was that the podman role would fully configure the
podman service, but we needed to run the podman_sdk role for socket
activation to be enabled.
It also meant that you needed to run the podman_sdk role after the
podman role (as it expected that podman was already installed) which is
not always desirable. For instance, in kayobe, we setup the virtualenv
before configuring the container engine.
Closes-Bug: #2054568 b28f9f1073ff028 42a38211a54
Change-Id: Ic9d3cf9ad94f0c