Call ansible tower fails because no extra vars are submitted #22476
Unanswered
BrGitHub11
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Hey, on your Tower Workflow tick the "PROMPT ON LAUNCH" checkbox and you should be good to go |
Beta Was this translation helpful? Give feedback.
1 reply
-
Looks like ManageIq is always using the method launch_ansible_job from the default domain. Does someone know who could help me with my questions? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm new to ManageIQ. So if I missed something in the documentation please provide the link. Thanks!
I'm running oparin-1.1.20230105135506_44ec8c4.
I'm trying to run a playbook after a VM was provisioned (this is a Service Catalog Item).
I put a Method into the PostProvision Instance which calls an Ansible Tower Job.
The deployment of the VM is successful.
The Ansible Tower Job is called but failing because no extra vars are provided by ManageIQ.
I tried to debug this issue looking into journalctls output.
When I take a look at the launch_ansible_job method there are a lot of log outputs, like "Processing Job Template" in the run function. But while I could see something like "Calling template.run_with_miq_job for template: ... AutomationManager::ConfigurationScript" I can't see a line "Processing Job Template" in the log.
I tried to insert lines like:
@handle.log(@warn, "findme")
or
$evm.log("warn", "findme")
into the code of launch_ansible_job but those are missing in the log output, too.
Could someone help me to figure out:
a) Why is there no log output? And how could I add debugging lines to the code?
b) Why are there no extra vars and no limit? How could I figure out why they are missing in the Ansible Tower Job call?
Any help is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions