Overcloud deployment fails when the designate related "designate_pool_manage" container runs: 2023-06-12 10:34:39.988752 | 525400b4-3bff-826e-b8aa-00000000e590 | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_5 | controller-0 | error={"changed": false, "msg": "Failed containers: designate_pool_manage"} 2023-06-12 10:34:39.989447 | 525400b4-3bff-826e-b8aa-00000000e590 | TIMING | tripleo_container_manage : Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_5 | controller-0 | 1:10:39.826209 | 3.24s There are two contributing causes, both found in the tripleo heat templates: - There is syntax error of "or or" in the designate policies in enable-secure-rbac.yaml - enforce_new_defaults is not set to true for the designate policies.
Edited the doc text for 17.1 beta release notes.
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