Podman service not started on Rocky 9

[Will Szumski]

I see the following error:

    Internal error: GET operation

during task: Ensure fluentd image is present for label check. It seems like the podman service isn't running and we do not have socket activation:

    [vagrant@controller0 vagrant]$ sudo systemctl status podman.socket
    ○ podman.socket - Podman API Socket
         Loaded: loaded (/usr/lib/systemd/system/podman.socket; disabled; preset: disabled)
         Active: inactive (dead)
       Triggers: ● podman.service
           Docs: man:podman-system-service(1)
         Listen: /run/podman/podman.sock (Stream)
    [vagrant@controller0 vagrant]$ sudo systemctl status podman.service
    ○ podman.service - Podman API Service
         Loaded: loaded (/usr/lib/systemd/system/podman.service; disabled; preset: disabled)
         Active: inactive (dead)
    TriggeredBy: ○ podman.socket
           Docs: man:podman-system-service(1)

[Will Szumski (willjs)]

Turns out I wasn't running the podman_sdk role:

https://github.com/openstack/ansible-collection-kolla/blob/master/roles/podman_sdk/tasks/main.yml#L65-L70

Seems like a slightly strange place to enable it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/909692

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/909692
Committed: https://opendev.org/openstack/ansible-collection-kolla/commit/70f3a398fdac299a78c39f389fa1dab91c36c55d
Submitter: "Zuul (22348)"
Branch: master

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.

    Closes-Bug: #2054568
    Change-Id: Ic9d3cf9ad94f0cb28f9f1073ff02842a38211a54

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ansible-collection-kolla 5.0.0.0rc1 release candidate.