Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

vagrant provision fails if pip setuptools < 17.1 in /vagrant #79

Open
dmccue opened this issue Aug 13, 2015 · 0 comments
Open

vagrant provision fails if pip setuptools < 17.1 in /vagrant #79

dmccue opened this issue Aug 13, 2015 · 0 comments

Comments

@dmccue
Copy link

dmccue commented Aug 13, 2015

Args:
vagrant provision

Symptoms:
==> default: Ran /vagrant/jenkins/share/eutester-base/bin/pip install --pre eutester returned 1
==> default: [2015-08-13T13:26:33+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Reason:
==> default: Downloading/unpacking mock (from eutester)
==> default: Running setup.py egg_info for package mock
==> default: mock requires setuptools>=17.1. Aborting installation
==> default: Complete output from command python setup.py egg_info:
==> default: mock requires setuptools>=17.1. Aborting installation

[root@ip-10-112-26-206 ~]# /vagrant/jenkins/share/eutester-base/bin/pip list | grep setuptools
setuptools (0.9.8)

Solution:
/vagrant/jenkins/share/eutester-base/bin/pip install --upgrade setuptools

This could be done manually but each 'vagrant provision' erases the previous alterations as it overwrites everything in /vagrant.
Can whatever creates /vagrant/jenkins/share/eutester-base/bin/pip (possibly cookbooks/micro-qa/recipes/eutester.rb) be adjusted so that it updates setuptools immediately afterwards?

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

No branches or pull requests

1 participant