OK, thanks Brian, that gives me some things to go on and I'm clearly in
need of going back and starting again to avoid this spaghetti.
Didn't know about the env variable rather than using those paths so will go
that route and that alone has been very helpful.
Thanks for your patience, just
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
Perhpas I have a misunderstanding here
When you say " no connection is involved"
If I'm right it is possible to ssh from a server to itself - shown by a new
shell and the ability to exit back to the previous shell - or am I mistaken
and it's somehow ignoring that
Is this not what ansible is
Thanks Brian
Not quite sure I understand, it's the output I'm trying to get (more of)
to understand why it's failing.
In case it helps at all
Here's the play 2 created that it fails on. This is fine to run directly
through ansible-playbook, just not through that play1
- hosts: nott
The import would not fail with connection issues, no connection is
involved, what is failing is a task, but you are not providing enough
output to determine which task it is.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible
I need help getting more information on why an import_ playbook fails
please
During a play (play 1) I'm (ansible.builtin.template) sucessfully
templating out another play (play 2) and variables file and using trying to
call them later in play 1, but that import fails
import_playbook:
