Puppet install on Ubuntu 16.04 LTS barfs on PIP

asked 2018-07-17 06:33:11 -0500

Things were going along swimmingly, when I got to this:

byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/tests/__init__.py to __init__.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/tests/scenario/__init__.py to __init__.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py to test_dashboard_basic_ops.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/__init__.py to __init__.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/config.py to config.pyc
byte-compiling /usr/local/lib/python2.7/dist-packages/tempest_horizon/plugin.py to plugin.pyc
running install_egg_info
Copying tempest_horizon.egg-info to /usr/local/lib/python2.7/dist-packages/tempest_horizon-0.0.1.dev22.egg-info
running install_scripts
+ pip install -U stestr os-testr
./run_tests.sh: line 245: pip: command not found

Seems like, what with all the Ubuntu packages that are installed, adding "python-pip" to the mix would have been one of them. This from a stock Ubuntu 16.04 server, and fresh Git install as per https://docs.openstack.org/puppet-openstack-guide/latest/install/deploy.html (https://docs.openstack.org/puppet-ope...) of last night. I have had to restart the install twice (once because the installer appears not to like btrfs when setting up a swap file, and once because the hostname didn't resolve properly, causing RabbitMQ install to barf), and then this hiccup. Proceeded apace (still running) after python-pip was installed.

edit retag flag offensive close merge delete