Overcloud deployment fails when deploying with CollectdEnableSensubility set to false CollectdEnableSensubility: false ------- 2023-03-07 18:31:50.274533 | 8ff94ee2-fe26-4db6-8066-e20d455c3d10 | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | controller-0 2023-03-07 18:31:50.313937 | 525400f8-6966-7fd1-0f94-00000000d68e | TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 2023-03-07 18:32:27.740380 | | WARNING | ERROR: Can't run container collectd stderr: Error: statfs /var/lib/tripleo-podman/collectd: no such file or directory 2023-03-07 18:32:27.742202 | 525400f8-6966-7fd1-0f94-00000000d68e | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | controller-0 | error={"changed": false, "msg": "Failed containers: collectd"} 2023-03-07 18:32:27.742859 | 525400f8-6966-7fd1-0f94-00000000d68e | TIMING | tripleo_container_manage : Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | controller-0 | 0:50:55.516071 | 37.43s If sensubility is disabled, the ansible module is not used, so the directory is not created. And there is no conditional in the volume list.
I've bumped the priority a bit here because deployment of collectd without sensubility breaking a deployment feels pretty high on the priority to resolve. If sensubility didn't work or failure to complete the collectd deployment was the only impact then I think medium makes sense, but since it was reported it stops the TripleO run at step 3, I think increasing the priority here makes sense.
Overcloud can be deployed with CollectdEnableSensubility set to false.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days