`ec2_group` module doesn't work with Mitogen 0.2.4

[jbscare]

With Mitogen 0.2.4, this playbook:

- hosts: localhost
  tasks:
    - ec2_group:
        name: jbstest
        description: JBS testing
        region: "{{ aws_region }}"
        vpc_id: "{{ vpc_id }}"
        rules: []
        rules_egress: []

Produces this output:

TASK [ec2_group] ***************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "boto3 required for this module"}

It works fine with Mitogen 0.2.2; it fails with 0.2.4, whether the security group already exists or not.

Here's a log with -vvv: ansible.log

[dw]

Same as #511

[dw]

Somehow explicit localhost's python_path has been broken. To confirm, do you have 'localhost' listed explicitly in your inventory? I see here by removing it (and receiving the default implicit localhost Ansible provides), the problem disappears.

This is almost certainly due to the python_path changes done during the delegate_to fiasco.

[jbscare]

Since you asked on #511, I tried your suggestion there; neither of -e ansible_python_interpreter=python nor -e ansible_python_interpreter=/usr/bin/python change the behavior for me.

We do have localhost explicitly in our inventory, so that we can set three host variables:

  localhost: 
    ansible_connection: local 
    readiness: ready 
    stack: prod 

Does the default localhost go via SSH rather than local?

(The other two variables are things that normally get set via the ec2.py inventory plugin, but localhost doesn't come from EC2, of course.)

[dw]

The implicit localhost gets ansible_connection=local and ansible_python_interpreter=[sys.executable], if you define it in inventory, it's just another host -- so ansible.cfg's transport setting by default, and IIRC just python or /usr/bin/python for ansible_python_interpreter.

I've found the problem and it's the opposite to what was expected -- somehow it is using my virtualenv Python interpreter path over SSH, which is completely wrong

[dw]

Kicking myself. I filed a bug to verify this stuff before cutting release, and didn't even make it through all the tickets. Fatigue :/ https://github.com/dw/mitogen/issues/476