With changes to config_template module that restored usage of {% raw %} tags [1]
renderring of mapping keys, if they're defined as variables, was broken.
Ansible, by design [2], does not render mapping keys. Moreover, it was not
working as intended anyway, since renderring happened in post-copy stage
so same records were not merged together, which resulted in #1812245
As such behaviour is expected by Ansible design, instead of adding some
workaround in config_template module, I suggest working around issue
by defining troublesome mapping with Jinja, that will allow it to render properly.
Reviewed: https:/ /review. opendev. org/c/openstack /openstack- ansible/ +/904856 /opendev. org/openstack/ openstack- ansible/ commit/ dbc265ce59d04a5 a5321f5a4c27c46 bf336692c4
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit dbc265ce59d04a5 a5321f5a4c27c46 bf336692c4
Author: Dmitriy Rabotyagov <email address hidden>
Date: Thu Jan 4 13:09:39 2024 +0100
Modify RGW client format
With changes to config_template module that restored usage of {% raw %} tags [1]
renderring of mapping keys, if they're defined as variables, was broken.
Ansible, by design [2], does not render mapping keys. Moreover, it was not
working as intended anyway, since renderring happened in post-copy stage
so same records were not merged together, which resulted in #1812245
As such behaviour is expected by Ansible design, instead of adding some
workaround in config_template module, I suggest working around issue
by defining troublesome mapping with Jinja, that will allow it to render properly.
[1] https:/ /review. opendev. org/c/openstack /ansible- config_ template/ +/881887 /github. com/ansible/ ansible/ issues/ 17324#issuecomm ent-685102595
[2] https:/
Closes-Bug: #2048036 6d817c620451799 c13d5d8938c 1ad9113f2a8dd54 efbdd72f63)
Related-Bug: #1812245
Change-Id: I8a32736239c632
(cherry picked from commit 4203aa26c6a0ae7