[openstack-dev] [stable] stable/kilo and stable/juno blocked on zake 0.2.2 release

Matt Riedemann mriedem at linux.vnet.ibm.com
Wed May 27 22:42:41 UTC 2015



On 5/27/2015 11:00 AM, Matt Riedemann wrote:
>
>
> On 5/27/2015 10:58 AM, Matt Riedemann wrote:
>>
>>
>> On 5/27/2015 10:57 AM, Matt Riedemann wrote:
>>> All changes to stable/kilo (and probably stable/juno) are broken due to
>>> a zake 0.2.2 release today which excludes kazoo 2.1.
>>>
>>> tooz 0.12 requires uncapped zake and kazoo so it's pulling in kazoo 2.1
>>> which zake 0.2.2 doesn't allow.
>>>
>>> ceilometer pulls in tooz.
>>>
>>> There is no stable/juno branch for tooz so that we can cap requirements
>>> for kazoo (since stable/juno g-r caps kazoo<=2.0).
>>>
>>> We need the oslo team to create a stable/juno branch for tooz, sync g-r
>>> from stable/juno to tooz on stable/juno and then do a release of tooz
>>> that will work for stable/juno - else fix kazoo and put out a 2.1.1
>>> release so that zake will start working with latest kazoo.
>>>
>>
>> Here is a link to the type of failure you'll see with this:
>>
>> http://logs.openstack.org/56/183656/4/check/check-grenade-dsvm/3acba73/logs/old/screen-s-proxy.txt.gz
>>
>>
>>
>
> Here is the tooz bug I reported for tracking:
>
> https://bugs.launchpad.net/python-tooz/+bug/1459322
>

Now that https://review.openstack.org/#/c/173117/ is merged we *should* 
be good for a short while on stable.

Hurry and approve and recheck all the things now before the next library 
release breaks everything again.

-- 

Thanks,

Matt Riedemann




More information about the OpenStack-dev mailing list