Hi all,

it took me sevceral days to understand what you were saying Alex and Heng

it looks like in this file:
./common_deploy_steps_tasks.yaml
paunch is not executed, or executed without logging?

paunch --verbose apply --file /var/lib/tripleo-config/container-startup-config-step_1.json --config-id tripleo_step1 --default-runtime podman --container-log-path /var/log/paunch.log
When I executed it manually, I got some errors:
https://pastebin.com/hnmW0rGX

According to some error messages, it might be, that it is trying to launch with value for log file: 

... '--log-driver', 'k8s-file', '--log-opt', 'path=/var/log/paunch.log/rabbitmq_init_logs.log' ...
2020-05-01 23:14:48.328 28129 ERROR paunch [  ] stderr: [conmon:e]: Failed to open log file Not a directory

... '--log-driver', 'k8s-file', '--log-opt', 'path=/var/log/paunch.log/mysql_init_logs.log' ...
020-05-01 23:14:48.812 28129 ERROR paunch [  ] stderr: [conmon:e]: Failed to open log file Not a directory

Also, i see it failed to enable in systemctl tripleo_memcached
"Failed to start memcached container."
and same for haproxy and keepalived...


Any ideas where to go further?