On Redhat distros (at least when using images built with DIB) the journal is only stored in memory. This makes it hard to debug issues where the host rebooted.
As a side note this seems to be required when using podman as a container engine (although arguably that ould be seen as kolla-ansible bug):
```
RUNNING HANDLER [common : Restart fluentd container] ************************************************************************************************************************
fatal: [controller0]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_container_payload_e4l_x66e/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_e4l_x66e/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 510, in recreate_or_restart_container\\n self.start_container()\\n File \"/tmp/ansible_kolla_container_payload_e4l_x66e/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 533, in start_container\\n self.create_container()\\n File \"/tmp/ansible_kolla_container_payload_e4l_x66e/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 496, in create_container\\n container = self.pc.containers.create(**args)\\n File \"/opt/kayobe/venvs/kolla-ansible/lib64/python3.9/site-packages/podman/domain/containers_create.py\", line 353, in create\\n response.raise_for_status(not_found=ImageNotFound)\\n File \"/opt/kayobe/venvs/kolla-ansible/lib64/python3.9/site-packages/podman/api/client.py\", line 75, in raise_for_status\\n raise APIError(cause, response=self._response, explanation=message)\\npodman.errors.exceptions.APIError: 500 Server Error: Internal Server Error (statfs /var/log/journal: no such file or directory)\\n'"}
```
Fix proposed to branch: master /review. opendev. org/c/openstack /kayobe/ +/909685
Review: https:/