Mitaka: pip_install_options break repo playbook

[Bjoern]

When setting pip_install_options to --force-reinstall it will break the repo playbook at:

TASK: [repo_build | Create OpenStack-Ansible requirement wheels] **************
failed: [infra03_repo_container-7bb818c0] => {"changed": true, "cmd": "pip wheel --timeout 120 --wheel-dir /tmp/openstack-wheel-output --find-links /var/www/repo/links --
find-links /tmp/openstack-wheel-output --constraint /var/www/repo/os-releases/13.3.8/requirements_constraints.txt --no-binary libvirt-python --extra-index-url https://rpc-repo.r
ackspace.com/pools --trusted-host rpc-repo.rackspace.com --build /tmp/openstack-builder --log /var/log/repo/repo_builder.log --requirement /var/www/repo/os-releases/13.3.8/requi
rements.txt --force-reinstall", "delta": "0:00:00.242903", "end": "2016-11-21 21:39:51.210082", "rc": 2, "start": "2016-11-21 21:39:50.967179", "warnings": []}
stderr:
Usage:
  pip wheel [options] <requirement specifier> ...
  pip wheel [options] -r <requirements file> ...
  pip wheel [options] [-e] <vcs project url> ...
  pip wheel [options] [-e] <local project path> ...
  pip wheel [options] <archive url/path> ...

no such option: --force-reinstall

FATAL: all hosts have already failed -- aborting

Seems like commit 4c620fee1f509d15009fdc18c3ad53cac7bd5f69 introduced this problem.
Perhaps we add a special repo_build_pip_install_options ?

[Jean-Philippe Evrard (jean-philippe-evrard)]

Please have at our triage discussion here:
http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-11-29.log.html#t2016-11-29T16:41:56

What we have to remember is the initial purpose of the pip_install_options: https://github.com/openstack/openstack-ansible-repo_build/blob/master/defaults/main.yml#L16-L19

We can think of revisiting this (for example splitting pip wheel/pip install behavior because the pip wheel options are not 100% the same as the pip install options), but if it's only for force-reinstall, we won't be revisiting this.

Could you explain more your use case please?

[Bjoern (bjoern-t)]

The pip_install_options was introduced prior to venvs to make sure that we always ensure pip and pip dependencies are correctly installed (which pip not always did). A --force-reinstall fixed most issues. I think we will experience those issues lesser since we have venvs but I might not rule out that we may use force-reinstall in the future again. Perhaps we should move as proposed with splitting the pip install options, one just for wheel building and the rest for the installation, as I had originally proposed

[Jean-Philippe Evrard (jean-philippe-evrard)]

https://bugs.launchpad.net/openstack-ansible/+bug/1643705

[Jean-Philippe Evrard (jean-philippe-evrard)]

Sorry, wrong link!

See the conversation of our bug triage: http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-12-06.log.html#t2016-12-06T16:44:58

[Major Hayden (rackerhacker)]

Mitaka has been EOL'd.