Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

aync

ANSIBLE VERSION

ansible --version
ansible 2.3.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
python version = 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2]

CONFIGURATION

OS / ENVIRONMENT

Ubuntu 14.04

SUMMARY

STEPS TO REPRODUCE

- hosts: localhost
name: 'async statu does not stop'
gather_facts: no
tasks:
- shell: sleep 30000
async: 10
poll: 0
register: job

- async_status: jid="{{job.ansible_job_id}}"
register: job_result
until: job_result.finished
retries: 500
delay: 5

EXPECTED RESULTS

In case the async job times out the async_status task needs to stop

ACTUAL RESULTS

async_status task keeps looping till it exhaust the retries

Using /home/seb/hgdata/sfdc-ops/ansible/ansible.cfg as config file

PLAY [async statu does not stop] ****************************************************************************************************************************************************************************

TASK [command] **********************************************************************************************************************************************************************************************
changed: [localhost] => {"ansible_job_id": "6215717693.6129", "changed": true, "finished": 0, "results_file": "/home/seb/.ansible_async/6215717693.6129", "started": 1}

TASK [async_status] *****************************************************************************************************************************************************************************************
FAILED - RETRYING: async_status (500 retries left).
FAILED - RETRYING: async_status (499 retries left).
FAILED - RETRYING: async_status (498 retries left).
FAILED - RETRYING: async_status (497 retries left).
FAILED - RETRYING: async_status (496 retries left).
FAILED - RETRYING: async_status (495 retries left).
FAILED - RETRYING: async_status (494 retries left).
FAILED - RETRYING: async_status (493 retries left).
^C [ERROR]: User interrupted execution

seb@seb:~/hgdata/sfdc-ops/scripts$ cat /home/seb/.ansible_async/6215717693.6129
{"started": 1, "finished": 0, "ansible_job_id": "6215717693.6129"}seb@seb:~/hgdata/sfdc-ops/scripts$

Issue 2:
Bug Report

COMPONENT NAME

LVM fact gathering

ANSIBLE VERSION

ansible 2.4.0
config file = /home/guru/docker/ansible.cfg
configured module search path = [u'/home/guru/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible-2.4.0-py2.7.egg/ansible
executable location = /bin/ansible
python version = 2.7.5 (default, Aug 2 2016, 04:20:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]

CONFIGURATION

defaults

OS / ENVIRONMENT

N/A

SUMMARY

The hash produced by fact gathering for ansible_lvm uses the LV name as the key, but you can have multiple LV's on a system with the exact same name. In this case, only the last LV discovered is shown in the hash.

STEPS TO REPRODUCE

Create LVs with same name in different VGs. for example:

# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
demo vg0 -wi-ao---- 1.00g
demo vg1 -wi-a----- 248.00m
# ansible localhost -m setup
...snip...
"ansible_lvm": {
"lvs": {
"demo": {
"size_g": "0.24",
"vg": "vg1"
}

EXPECTED RESULTS

Given data structure I guess the most I could hope for is an error. What I need is for both LVs to be listed even though they have the same name. Not sure how the LVM facts section could best be refactored to support this...

ACTUAL RESULTS

Only the last LV seen is shown, the other(s) become invisible.