To Reproduce Steps to reproduce the behavior:

1. Use the CinderRbdMultiConfig THT parameter to define multiple cinder RBD backends
2. After the deployment, check the ceph keyring files on the Compute nodes, and note that the files are named incorrectly. A file that should be named "/etc/ceph/CLUSTER.client.USER.keyring" is missing a '.' and is incorrectly named "/etc/ceph/CLUSTER.clientUSER.keyring"

Expected behavior

• The keyring file is named correctly

Bug impact

• The bug impacts a customer that filed an SE to allow them to use the CinderRbdMultiConfig parameter to configure multiple cinder RBD backends. This is an existing customer that wants to migrate from a non-director deployed 16.2 release to a fully supported (director deployed) 17.1.
• See https://issues.redhat.com/browse/SUPPORTEX-24913

Known workaround

• None.

Additional context

• The regression was introduced by https://gitlab.cee.redhat.com/eng/openstack/openstack-tripleo-heat-templates/-/commit/4525808e71b0671d5a49dd7580f60f844a35bd1c, but it should NOT be treated as an escape!
• The reason it is not an escape is the CinderRbdMultiConfig feature was never officially supported in 17.1 due to QE constraints, see https://issues.redhat.com/browse/OSP-2989