Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provisioning failing on pip dependencies #1

Open
ieaves opened this issue Feb 7, 2017 · 0 comments
Open

provisioning failing on pip dependencies #1

ieaves opened this issue Feb 7, 2017 · 0 comments

Comments

@ieaves
Copy link
Collaborator

ieaves commented Feb 7, 2017

Currently vagrant provision fails, erroring out with a wall of useless text. I can't track down the root cause but I am able to reach a solution.

Looking at this bug report from ansible ansible/ansible-modules-core#5347 I thought pip might be executing using the python 2 pip executable, and having reached a permission error elevated the pip permissioning to use sudo creating an ansible task of

  • name: Install pip dependencies
    become: yes
    pip: executable="/usr/bin/pip3"
    chdir="{{ local_dev_path }}"
    requirements="{{ local_dev_path }}/{{ item }}"
    with_items:
    - requirements.txt

Attempting to provision with this modification will actually break pip causing all uses of pip to land with the following error:

ImportError: No module named 'packaging'

However, reinstalling pip directly through the get-pip script will correct the error. Re-installing pip through any other means does not appear to correct the issue

sudo -i
apt-get purge -y python3-pip
wget https://bootstrap.pypa.io/get-pip.py
python3 ./get-pip.py
apt-get install python3-pip

If you ssh into the box, update pip using the above and re-provision. Voila, provisioning will be successful.

As to why? Fuck if I know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant