pip 10 breaks "pip install", which with out packages

Bug #1764369 reported by Jeffrey Zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Undecided
Unassigned

Bug Description

pip 10 breaks "pip install", which with out packages.

error logs from CI http://logs.openstack.org/periodic-stable/git.openstack.org/openstack/kolla/stable/ocata/kolla-publish-centos-source/d281838/logs/build/nova-compute.txt.gz

(test) jeffrey@t470p:~$ pip --version
pip 10.0.0 from /home/jeffrey/.dotfiles/virtualenvs/test/lib/python2.7/site-packages/pip (python 2.7)
(test) jeffrey@t470p:~$ pip install
ERROR: You must give at least one requirement to install (see "pip help install")
(test) jeffrey@t470p:~$ echo $?
1
(test) jeffrey@t470p:~$ pip install -U 'pip<10'
Looking in indexes: http://pypi.douban.com/simple
Collecting pip<10
  Downloading http://pypi.doubanio.com/packages/ac/95/a05b56bb975efa78d3557efa36acaf9cf5d2fd0ee0062060493687432e03/pip-9.0.3-py2.py3-none-any.whl (1.4MB)
    100% |████████████████████████████████| 1.4MB 12.3MB/s
vmha 0.0.1.dev20 requires keystoneauth1, which is not installed.
vmha 0.0.1.dev20 requires python-novaclient, which is not installed.
vmha 0.0.1.dev20 requires tooz, which is not installed.
pecan 1.3.2 requires logutils>=0.3, which is not installed.
pecan 1.3.2 requires WebTest>=1.3.1, which is not installed.
zuul 2.6.0 has requirement GitPython<2.1.2,>=0.3.3, but you'll have gitpython 2.1.8 which is incompatible.
Installing collected packages: pip
  Found existing installation: pip 10.0.0
    Uninstalling pip-10.0.0:
      Successfully uninstalled pip-10.0.0
Successfully installed pip-9.0.3
(test) jeffrey@t470p:~$ pip --version
pip 9.0.3 from /home/jeffrey/.dotfiles/virtualenvs/test/lib/python2.7/site-packages (python 2.7)
(test) jeffrey@t470p:~$ pip install
You must give at least one requirement to install (see "pip help install")
(test) jeffrey@t470p:~$ echo $?
0

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

since pike, this is fixed by https://review.openstack.org/#/c/413861/, so this issue only happens on ocata branch.

Changed in kolla:
milestone: none → 4.0.4
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561573

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/ocata)

Reviewed: https://review.openstack.org/561573
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=67b092ead7bd3395a8e0b71abdf20710de2c78dd
Submitter: Zuul
Branch: stable/ocata

commit 67b092ead7bd3395a8e0b71abdf20710de2c78dd
Author: Jeffrey Zhang <email address hidden>
Date: Mon Apr 2 09:09:24 2018 +0800

    Fix ocata branch gate

    This patch is include five backport commits.

    Gate fix: Cap hacking to avoid gate failure

    hacking is not capped in g-r and it is in
    blacklist for requirement as hacking new version
    can break the gate jobs.

    Hacking can break gate jobs because of various
    reasons:
    - There might be new rule addition in hacking
    - Some rules becomes default from non-default
    - Updates in pycodestyle etc

    That was the main reason it was not added in g-r
    auto sync also. Most of the project maintained the
    compatible and cap the hacking version in
    test-requirements.txt and update to new version when
    project is ready. Bumping new version might need code
    fix also on project side depends on what new in that
    version.

    If project does not have cap the hacking version then,
    there is possibility of gate failure whenever new hacking
    version is released by QA team.

    Example of such failure in recent release of hacking 1.1.0
    -
    http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html

    Move ansible to virtualenv in kolla_toolbox

    Now the ansible and its python dependencies are installed on system. It
    may be failed to install in some case. This patch installs python
    packages in virtualenv for kolla_toolbox image.

    Closes-Bug: #1771717
    (cherry picked from commit ce31fa4b1c85de4c21ffb63f3cf58e02bfd3d0a4)

    base: set $contentdir for CentOS

    CentOS recently started syncing alternate arch repos to mirrors. And to
    make it easier to play with centos-* packages idea of 'contentdir'
    appeared.

    https://lists.centos.org/pipermail/centos-devel/2018-March/016542.html
    (cherry picked from commit ec5daaaa634351d24706e605c2c6726be402d35b)

    base: bump centos-release-qemu-ev for oraclelinux

    (cherry picked from commit 2f271522589e5d2956611787508b5b3ae44ca84b)

    Skip pip install when packages variable is empty

    pip 10 is release recently. `pip install` without any package will raise
    an error now.

    Closes-Bug: #1764369
    Change-Id: Ic81181b8b87ccbac489d993f05c125e224922077

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 4.0.5

This issue was fixed in the openstack/kolla 4.0.5 release.

Changed in kolla:
milestone: 4.0.4 → 4.0.5
Changed in kolla:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.