ansible-playbook hangs on lxc containers

[pgauret]

SUMMARY

ansible-playbook hangs at the "PLAY RECAP" stage when applying changes to lxc containers (through ansible_connection: lxc).

ISSUE TYPE

• Bug Report

COMPONENT NAME

ansible_connection: lxc

ANSIBLE VERSION

  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.6/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.6.8 (default, Mar 13 2019, 17:23:12) [GCC 8.3.0]

CONFIGURATION

"ansible-config dump --only-changed" didn't return anything.

/etc/ansible/hosts

all:
  vars:
      ansible_python_interpreter: /usr/bin/python3  
  hosts:
      localhost:
          ansible_connection: local
      gw:
          ansible_connection: lxc 

OS / ENVIRONMENT

Alpine Linux 3.9.2 (on ansible host and target containers)
Kernel 4.19
lxc-3.1.0
py3-lxc-3.0.3

STEPS TO REPRODUCE

Running any simple playbook against a lxc container with ansible_connection: lxc

EXPECTED RESULTS

Expecting ansible-playbook to terminate successfully and return to shell

ACTUAL RESULTS

ansible-playbook actually performs the changes fine but hangs at the PLAY RECAP stage, requires ^C to return to shell.

Extract of the relevant log

PLAY [web] *************************************************************************************************************************************************************************************************
skipping: no hosts matched

PLAY RECAP *************************************************************************************************************************************************************************************************
gw                         : ok=2    changed=0    unreachable=0    failed=0   

^C [ERROR]: User interrupted execution

Full session log

https://gist.github.com/pgauret/bd3676ae64eeed015175aa96987c054d

[ansibot]

Files identified in the description:
None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[pgauret]

Still stuck on this. Attaching the end of a debug trace showing where I think ansible-playbook gets stuck. Not sure of what it is trying to do and why it somehow fails though.

https://gist.github.com/pgauret/9acb8574a9e4ac2751df33dfbf35d212

[s-hertel]

Hi!

Thank you very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute.

If this is still an issue for you, please open an issue in https://github.com/ansible-collections/community.general where the connection plugin is maintained.

Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.

See this page for a complete and up to date list of communication channels and their purposes:

• https://docs.ansible.com/ansible/latest/community/communication.html

Thank you once again for this and your interest in Ansible!