-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible -B does not return ansible_job_id (page 37) #91
Comments
Thanks for reporting this; I'll do a little digging. |
Same here. |
I'm seeing this as well. |
@wtnebel - They should... but they don't always. I would recommend adding feedback to the upstream issue ansible/ansible#15988 |
Still waiting on a response for that one. Thanks Jeff! Does anyone have an example set-up of it working correctly? I'm wondering if there's some issue with my specific versions/distributions of Ansible/Python/Host OS/Target OS. |
Looks like there is a change in the pipeline that will address this issue soon: |
Well... that was merged, and is in |
Using Ansible 2.8.3:
Using latest
|
Hmm... it seems polling doesn't work though—it waits until the very end and then gives all the job statuses. If I add At least the job IDs can be dumped if using |
To give more clarity:
Ends up dumping:
But the following:
Sits forever. I would think it should poll every 10 seconds? If I add in The docs do indicate that polling should work like I'd expect... https://docs.ansible.com/ansible/latest/user_guide/intro_adhoc.html#time-limited-background-operations |
Tried with:
(Failed == there seemed to be no live polling) |
Ansible 1.9.1 help:
Ansible 2.8.4 help:
|
I opened an upstream issue: ansible/ansible#61015 |
Actual upstream issue to follow: ansible/ansible#14681 |
For now I'll update that section of the book to mention background tasks, but mention that polling does not work with realtime CLI output, so you can either run the task and it will complete and give final output and Job IDs, or run the task and immediately background it with |
Closing this issue as the text will now default to presuming |
This appears to be a long-standing issue with Ansible, as seen here:
ansible/ansible#15988
I commented on that thread with what I found, but I will copy+paste it here as well:
Attempting to do the ad-hoc command of:
ansible multi -b -B 3600 -a "yum -y update"
only returns:
when it should be returning something like:
The text was updated successfully, but these errors were encountered: