Comment 11 for bug 1763966

It appears that this "fix" might now be creating a new problem. While two days ago my devstack installation (script) worked fine, now it ends with this error:

+stack.sh:main:802 install_infra
+lib/infra:install_infra:31 local PIP_VIRTUAL_ENV=/opt/stack/requirements/.venv
+lib/infra:install_infra:32 '[' '!' -d /opt/stack/requirements/.venv ']'
+lib/infra:install_infra:32 virtualenv /opt/stack/requirements/.venv
New python executable in /opt/stack/requirements/.venv/bin/python
Complete output from command /opt/stack/requirements/.venv/bin/python -m pip config list:
ERROR: unknown command "config"
----------------------------------------
Traceback (most recent call last):
  File "/bin/virtualenv", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 793, in main
    symlink=options.symlink,
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 1087, in create_environment
    install_wheel(to_install, py_executable, search_dirs, download=download)
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 935, in install_wheel
    _install_wheel_with_search_dir(download, project_names, py_executable, search_dirs)
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 964, in _install_wheel_with_search_dir
    config = _pip_config(py_executable, python_path)
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 1038, in _pip_config
    remove_from_env=["PIP_VERBOSE", "PIP_QUIET"],
  File "/usr/lib/python2.7/site-packages/virtualenv.py", line 886, in call_subprocess
    raise OSError("Command {} failed with error code {}".format(cmd_desc, proc.returncode))
OSError: Command /opt/stack/requirements/.venv/bin/python -m pip config list failed with error code 1

In the earlier logging you can see that pip is downgraded from version 19.0.1 to 9.0.3, the older version does not support the "config" command. So for some reason the "wrong" version ends up in the venv. If you remove the "fix", the old problem return, so that is not an option. As far as i can tell i did not change anything. What might be related is that on January 22nd pip version 19 was released. But stack.sh does too many things around pip to be certain what is going wrong. And it also uses "https://bootstrap.pypa.io/get-pip.py", to get a new pip version, so it is difficult to see which pip version is used when.

I run devstack on a centos-7 (virtual) machine. But i don't think the distro is relevant. Apart from the pip 19 release i don't see any obvious reasons why this suddenly stopped working