Ansible 2.2.0.0: Variables in handler names not populated #19898
Labels
affects_2.2
This issue/PR affects Ansible v2.2
bug
This issue/PR relates to a bug.
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
Issue Type: Bug Report, Regression from #15713
Component Name: handlers
Ansible Version: 2.2.0.0
Environment: OS X 10.11.6
Summary: Under Ansible 2.2.0.0, Jinja variables contained in a handler
name
are no longer populated. Under Ansible 1.9.x and 2.1.1.0, they were populated. Here's a quick example:Steps To Reproduce:
Write this content to
playbook.yml
:Run the playbook:
ansible-playbook --connection=local playbook.yml
Expected Results: In the output of the playbook run, any mention of
{{ appname }}
should not appear, but replaced withsomeapp
, per the given variables.Actual Results:
Note that in the
RUNNING HANDLER
line, the Jinja template syntax is printed literally, rather than being populated with the variable that clearly exists, since it's populated elsewhere. This is a regression from 1.9.x and 2.1.1.0.The text was updated successfully, but these errors were encountered: