Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ec2.py fails with - NameError: name 'botocore' is not defined - on devel #17555
OS / ENVIRONMENT
Used to only require
Which I believe is a bug because it doesn't really tell the user what's wrong. Especially because this only happens if the user is testing
Additionally, if the user removes
If the user installs both
What I find strange about this is that the script fails based on the version of ansible.
STEPS TO REPRODUCE
virtualenv ansible . ./ansible/bin/activate pip install ansible boto wget https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.ini wget https://raw.github.com/ansible/ansible/devel/contrib/inventory/ec2.py python ec2.py
virtualenv ansible . ./ansible/bin/activate # pip install ansible boto boto3 works! pip install ansible boto3 wget https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.ini wget https://raw.github.com/ansible/ansible/devel/contrib/inventory/ec2.py python ec2.py
ec2.py should announce that either:
It would appear that two working states are available now:
If those are the desired states then I would consider this fixed!
@xenithorb if I read you msg correctly ec2.py now works with boto and boto3 ? as it's not working for me and my setup is standard nothing but does it work with Python 3.6.3 ?
Both boto are installed for both versions of python:
I would expect as a user of ec2.py for dynamic EC2 inventory for this to work with python3, does it ?
If there is something incorrect with the setup I have let me know, as I've always used ec2.py with python2.7 and boto but since boto3 works with python3.6 it makes sense for these to both co-exist on the ansible control machine in harmony.
As I'd rather not do virtualenv or miniconda environments and take it off our RHEL/CentOS yum standard package install/upgrade path.