Description of problem:
Problem appears when customer uses the required format [1] on the logging-environment-rsyslog.yaml environment file, the overcloud deployment injects the Elasticsearch servers array in the following incorrect format to the rsyslog containers:  server="[10.28.26.224, 10.28.26.225, 10.28.26.226]" which is not supported by rsyslog and causes the following container error: 

rsyslogd: omelasticsearch: we are suspending ourselfs due to server failure 3: Host name '[10.28.26.224, 10.28.26.225, 10.28.26.226]' contains bad letter [v8.1911.0-3.el8 try https://www.rsyslog.com/e/2007 ] 

rsyslog configuration specifies the required format for an array of Elastisearch servers in [1]: server=["elasticsearch1", "elasticsearch2"]. When customer directly modifies the rsyslog container configuration using this specific format, rsyslog works properly and logs are sent to Elasticsearch. 


Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-11.3.2-1.20210104205664.el8ost.2.noarch

How reproducible:


Steps to Reproduce:
1. Deploy with following syntax in logging-environment-rsyslog.yaml
    server: ["10.28.26.224", "10.28.26.225", "10.28.26.226"]


Actual results:
Incorrect format is deployed to the rsyslog containers:  
server="[10.28.26.224, 10.28.26.225, 10.28.26.226]" which is not supported by rsyslog and causes the following container error: 

rsyslogd: omelasticsearch: we are suspending ourselfs due to server failure 3: Host name '[10.28.26.224, 10.28.26.225, 10.28.26.226]' contains bad letter [v8.1911.0-3.el8 try https://www.rsyslog.com/e/2007 ] 



Expected results:
following format deployed to rsyslog containers:
server=["elasticsearch1", "elasticsearch2"]


Additional info:

Actual deployed
    server="[10.28.26.224, 10.28.26.225, 10.28.26.226]"
Expected deployed:
    server=["elasticsearch1", "elasticsearch2"]