Hi All,
I know a lot of the infra team are in Germany for the sprint, howveer I'm
see what seems like a lot of upper-constraint bumps that are failing due to
mirrors being out of sync.The most recent example of this is https://review.openstack.org/374469/ where you can see: --- Could not find a version that satisfies the requirement openstacksdk===0.9.7 (from -c /opt/stack/new/requirements/upper-constraints.txt (line 205)) (from versions: 0.6.0, 0.6.1, 0.6.2, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6) --- Checking pypi[2] shows: ... openstacksdk-0.9.7.tar.gz openstacksdk-0.8.6-py2.py3-none-any.whl openstacksdk-0.9.7-py2.py3-none-any.whl openstacksdk-0.7.3.tar.gz ... But the mirror for that job[3] shows: ... openstacksdk-0.9.5.tar.gz openstacksdk-0.9.6.tar.gz ... Is there some what we can frob the mirrors? or add a fallback to pypi if the requested pacakge isn't there? Yours Tony. [1] http://logs.openstack.org/69/374469/2/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/e9af99d/logs/devstacklog.txt.gz#_2016-09-22_02_02_48_865 [2] https://pypi.python.org/simple/openstacksdk/ [3] http://mirror.mtl01.internap.openstack.org/pypi/simple/openstacksdk/
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
