I am pretty new to ansible. I looked at docs and such but it was not too 
clear for me yet. 

at some point in a playbook, the following sequence was executed via the 
shell module in some yaml file:

     scl enable rh-git29 bash

At that moment the playbook stops dead in it's tracks as the remote end 
executes a shell and never comes back. It hangs.
If this observation is true, I don't understand why it could work in the 
first place.
Is this conclusion true?

Secondly, as the only thing the command does is sourcing in a file (needed 
for the rest of the playbook?)
I changed it into:

    source /opt/rh/rh-git29/enable

I know that the vars are not retained between playbooks this way and is not 
needed. But is it retained 
within the playbook run itself?

E.g. all folow-up still see the environment set? And does that also hold 
for any task that's included?

(like: - include_tasks: create-something.yml)

Roeland





-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to