Open Stack

Tony,

Thanks for digging into this!

I should be able to help, but right now we're ramping up for the L3
feature freeze and there are a lot of release-related activities going
on. Can this wait a few weeks for things to settle down again?

Doug

Excerpts from Tony Breeds's message of 2015-08-24 19:57:52 +1000:
> Hi All,
>     Firstly I apologise for the rambling nature of this email.  There's a lot
> of context/data here and I'm not sure of the best way to present it.
> 
> In [1] we discovered that stable/juno devstack is broken.  After a little digging
> we opened [2]  This required creating a stable/juno branch for python-swiftclient
> (done), raising the upper cap of python-swiftclient from <=2.3.1 to <2.4.0
> (done) and releasing 2.3.2 (in progress).
> 
> The change in upper limits for python-swiftclient has created several reviews
> (about 20).  Why am I telling you this?  Several of those reviews seem to be
> stuck on oslo related issues.
> 
> * openstack/python-ceilometerclient :: https://review.openstack.org/#/c/173126/
>      It looks like it's getting 2.2.0 of oslo.i18n but it should capped at 1.3.1 in stable/juno
>      ---
>  Collecting oslo.utils<1.5.0,>=1.4.0 (from -r /home/jenkins/workspace/gate-python-ceilometerclient-python27/requirements.txt (line 4))
>    Downloading http://pypi.ORD.openstack.org/packages/py2.py3/o/oslo.utils/oslo.utils-1.4.0-py2.py3-none-any.whl (55kB)
>  Collecting oslo.i18n>=1.3.0 (from oslo.utils<1.5.0,>=1.4.0->-r /home/jenkins/workspace/gate-python-ceilometerclient-python27/requirements.txt (line 4))
>    Downloading http://pypi.ORD.openstack.org/packages/py2.py3/o/oslo.i18n/oslo.i18n-2.2.0-py2.py3-none-any.whl
>      ---
>     I think this means we need an oslo.utils 1.4.1 release with the
> requirements capped from g-r.  There isn't a stable/juno branch for oslo.utils
> so would we need to make one based on 1.4.0?
> 
>  * openstack/pycadf :: https://review.openstack.org/#/c/206719/
> ---
>  Collecting oslo.messaging<1.5.0,>=1.4.0 (from -r /home/jenkins/workspace/gate-pycadf-python26/test-requirements.txt (line 12))
>   Downloading http://pypi.DFW.openstack.org/packages/py2/o/oslo.messaging/oslo.messaging-1.4.1-py2-none-any.whl (129kB)
>  Collecting oslo.utils>=0.2.0 (from oslo.messaging<1.5.0,>=1.4.0->-r /home/jenkins/workspace/gate-pycadf-python26/test-requirements.txt (line 12))
>    Downloading http://pypi.DFW.openstack.org/packages/py2.py3/o/oslo.utils/oslo.utils-2.2.0-py2.py3-none-any.whl (58kB)
> ---
>     Which I think needs a 1.4.2 release of oslo.messaging with requirements capped from g-r
> 
>  * openstack/oslo.i18n :: https://review.openstack.org/#/c/206714
>     This is failing with "AttributeError: assert_calls"  I think this is
>     because we're installing mock 1.3.0 but mock should be capped at 1.0.1 in
>     stable/juno
> ---
>  Collecting oslotest<1.4.0,>=1.1.0 (from -r /home/jenkins/workspace/gate-oslo.i18n-python26/test-requirements.txt (line 4))
>   Downloading http://pypi.region-b.geo-1.openstack.org/packages/py2.py3/o/oslotest/oslotest-1.3.0-py2.py3-none-any.whl
> Collecting mock>=1.0 (from oslotest<1.4.0,>=1.1.0->-r /home/jenkins/workspace/gate-oslo.i18n-python26/test-requirements.txt (line 4))
>   Downloading http://pypi.region-b.geo-1.openstack.org/packages/2.7/m/mock/mock-1.3.0-py2.py3-none-any.whl (56kB)
> ---
>     I think this means that we need oslotest 1.3.1 which the versions capped
> from g-r.  As with oslo.utils I think this needs a new branch?
> 
> There are several other issues in other projects but I figured I had to start
> somewhere.
> 
> To be clear I'm happy to propose patches to do these things (but clearly I
> can't make branches or cut releases).  I'm also very happy to be told I'm doing
> this wrong and my conclusions are incorrect (bonus points if you help me find
> the right solution).
> 
> Yours Tony.
> 
> [1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/072193.html
> [2] https://bugs.launchpad.net/python-swiftclient/+bug/1486576