Thanks, that can be useful.
On Saturday, December 5, 2015 at 1:39:22 AM UTC-5, Brian Coca wrote:
>
> no, but you can try something like this:
> ```
> - debug: msg="execute {{handler}}"
> changed_when: True
> when: handler is defined
> notify: "{{handler}}"
> tags: ['handler']
>
We have playbook that didn't have the force_handlers directive. They ended
up failing and of course, they re-run instead and the handlers never got
run for completed tasks.
I've searched but couldn't find something related to run a specific tasks
which would be the handler itself. Something
If you use disablerepo=base,updates,extras it seems to work. the Wildcard
doesn't seem to work. ???
On Thursday, October 22, 2015 at 9:46:00 AM UTC-4, Steve Malenfant wrote:
>
> I've got the same problem here on both 1.9.2 and 1.9.4. You need some
> "unreachable" repos in yo
I've got the same problem here on both 1.9.2 and 1.9.4. You need some
"unreachable" repos in your /etc/yum.repos.d configured to reproduce.
Example :
I'm using this here "yum: name={{ item }} disablerepo=* enablerepo=private*
state=present" and the output is like this :
failed:
I'm running into a little problem trying to register a variable with a |
in it. Anybody know how to escape those?
I've got this template :
{% for sections in transforms_conf %}
[{{ sections.section }}]
{% for options in sections.options %}
{% for option, value in options.iteritems() %}
{{
