This affects deployments where there is more than one redis instance, including the typical 3 controller default deployment. Deployments with tls-e are more severely affected as redis instances aren't configured in a way that allows them to replicate. By default, environments/services/octavia.yaml, environments/services/designate.yaml and environments/enable-designate.yaml use the non-pacemaker version of the redis template. The non-pacemaker version likely hasn't been tested in HA environments and doesn't include configuration support for tls-e. Some possible options: - separate ha environemnt files for octavia and designate to include redis - make pacemaker a requirement for octavia and designate and have the default environment files include the pacemaker redis instead - create a non-pacemaker dependent version of the redis deployment
An immediate workaround is to make sure environments/ha-redis.yaml is included in the overcloud deploy command line after designate or octavia is specified on the command line.
*** Bug 2161968 has been marked as a duplicate of this bug. ***
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