Hi Sean, To start with, "pip install PyECLib==1.0.9" works fine on a clean trusty instance. Looking at the gate log - http://logs.openstack.org/92/115092/11/check/gate-grenade-dsvm/ecfb1f5/logs/grenade.sh.txt.gz#_2015-09-10_13_54_32_069: -[snip]- 2015-09-10 13:55:52.335 | Collecting PyECLib===1.0.7 (from -c /opt/stack/new/requirements/upper-constraints.txt (line 15)) 2015-09-10 13:55:52.393 | Downloading http://pypi.region-b.geo-1.openstack.org/packages/source/P/PyECLib/PyECLib-1.0.7.tar.gz (8.4MB) -[snip]- If requirements.txt has "PyECLib >= 1.0.7", and latest on PyPI is PyECLib 1.0.9, I wonder why the slave is trying to pull 1.0.7 .. Also how is "upper-constaints.txt" used? Thanks Tushar -----Original Message----- From: Sean Dague [mailto:sean at dague.net] Sent: Thursday, September 10, 2015 7:44 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org> Subject: [openstack-dev] [gate] broken by pyeclib 1.0.9 release The pyeclib 1.0.9 release has broken the gate because Swift is in the default grenade upgrade jobs, and Swift stable/kilo allows 1.0.9 (which doesn't compile correctly with a pip install). We're working to pin requirements in kilo/juno right now, but anything that has a grenade job is going to fail until these land. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev