[openstack-dev] [Openstack-stable-maint] Stable check of openstack/horizon failed

Julie Pichon jpichon at redhat.com
Mon Jan 26 11:01:29 UTC 2015


On 26/01/15 10:49, Ihar Hrachyshka wrote:
> On 01/26/2015 11:00 AM, Julie Pichon wrote:
>> On 26/01/15 06:34, A mailing list for the OpenStack Stable Branch test
>> reports. wrote:
>>> Build failed.
>>>
>>> - periodic-horizon-docs-icehouse
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-docs-icehouse/9382030/
>>> : SUCCESS in 4m 14s
>>> - periodic-horizon-python26-icehouse
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-python26-icehouse/b39cce4/
>>> : FAILURE in 2m 53s
>>> - periodic-horizon-python27-icehouse
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-python27-icehouse/2381739/
>>> : FAILURE in 3m 09s
>>> - periodic-horizon-docs-juno
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-docs-juno/3e9efb0/
>>> : SUCCESS in 5m 01s
>>> - periodic-horizon-python26-juno
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-python26-juno/efc60ca/
>>> : FAILURE in 3m 19s
>>> - periodic-horizon-python27-juno
>>> http://logs.openstack.org/periodic-stableperiodic-horizon-python27-juno/59627d3/
>>> : FAILURE in 2m 22s
>> This is being debugged at
>> https://bugs.launchpad.net/horizon/+bug/1413876 , the patch for
>> django_openstack_auth is merging. Once a new version of the library is
>> released that includes the fix, this should resolve the problem on all
>> branches without the need for backports.
> 
> 
> Should we also update openstack/requirements for all branches not to
> pick the failing version of the library?

There was a brief discussion about setting an upper limit pin, but a
"negative" version pin to avoid the broken release would be a lot
cleaner indeed. I'll prepare the patches. Thanks!

Julie




More information about the OpenStack-dev mailing list