I don't think adding --no-use-wheel to the 'upgrade_format' command (lines 260/310 above) will fix this. If the particular package (specifically pip) is already at the latest available version in the virtualenv, pip does nothing.
I have been using the following patch locally to get around this issue: https://review.openstack.org/84081
I don't think adding --no-use-wheel to the 'upgrade_format' command (lines 260/310 above) will fix this.
If the particular package (specifically pip) is already at the latest available version in the virtualenv, pip does nothing.
I have been using the following patch locally to get around this issue: https:/ /review. openstack. org/84081