In order to work around early issues encountered with cinder trying to use etcd for its distributed lock manager in a tls-e deployment, a new THT parameter was introduced by [1] that controls whether etcd (and cinder) actually use TLS. [1] https://review.opendev.org/717837 The new EnableEtcdInternalTLS defaults to False. Full support for TLS is possible when tls-e is deployed using tripleo-ipa (see bug #1823932), but that is not the default tls-e deployment in Train. Train still defaults to using novajoin, which needs to be fixed in order for etcd to support TLS (see bug #1843701). In other words, once bug #1843701 is fixed it will be possible to deploy etcd with TLS. At that point, the EnableEtcdInternalTLS should default to True.
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.0 (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-2022:6543