When I say 'no connection is involved' it is in the act of importing a
playbook, this is a 'LOCAL ACTION' that has nothing to do with a
remote, so if it fails it will not give a connection error.

One of many issues with your play is that you are trying to import a
playbook inside a play, this does not work and you should get a
specific error message, your connection issue might be making the play
fail before you get there and that is another problem, but again, not
enough info to debug with. You also cannot register the result of an
import or include nor ignore import errors.

Also, you cannot use env vars like this $LINUX_PLAYBOOKS, use the 'env' lookup

-- 
----------
Brian Coca

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CACVha7feQa9%2BVgAWZAVZWmW-st2iQ85047UoRDrkJYMQEzfqsg%40mail.gmail.com.

Reply via email to