Ansible output is not displayed

Issue Type

• Bug report

Molecule and Ansible details

ansible [core 2.11.4]
  config file = None
  configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/user/.virtualenvs/mol/lib/python3.7/site-packages/ansible
  ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/user/.virtualenvs/mol/bin/ansible
  python version = 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
  jinja version = 3.0.1
  libyaml = True
molecule 3.4.0 using python 3.7
    ansible:2.11.4
    delegated:3.4.0 from molecule

Molecule installation method:

• pip

Ansible installation method:

• pip

Detail any linters or test runners used:

Desired Behavior

When runing a molecule command, the ansible output gets displayed

Actual Behaviour

When running a molecule command, all the molecule output is displayed but not the ansible-playbook output (i.e “PLAY … TASK…”).

To reproduce the issue, I used this simple script named test.sh in my test directory:

#!/bin/bash
VERSION=${1:-HEAD}
if [ "$VERSION" == "HEAD" ];then
  pip install molecule ansible
else
  pip install molecule==3.1.5 ansible==2.9.25
fi
ansible --version && molecule --version
rm -rf myrole
molecule init role myrole
cd myrole || return
molecule --debug destroy

• I created a virtualenv and ran ./test.sh to install last version of molecule and ansible and execute a molecule destroy and got no ansible output
• I created another virtualenv and ran ./test.sh 1 to install version 3.1.5 of molecule and version 2.9.25 of ansible and this time got the expected ansible

I posted the complete output here

I used the molecule destroy command as it is the easiest reproducible example but I experience the same issue with molecule converge or molecule test.

I tried on debian buster (python 3.7) and ubuntu focal (python 3.8)

[ssbarnea]

I think i found the bug, try to add subprocess-tee!=0.3.3 and tell me if it is fixing your problem, if confirmed I will yank that release made yesterday and look for a fix for it.

[ssbarnea]

I just yanked the 0.3.3 release and created https://github.com/pycontribs/subprocess-tee/issues/46 for tracking. Rerunning CI jobs should be enough. For local, you may want to recreate the virtualenvs to remove the rotten apple.