[openstack-dev] [all] Problems with keystoneclient stable branch (and maybe yours too)

gordon chung gord at live.ca
Tue Apr 14 02:33:10 UTC 2015

>> 2) Incorrect cap in requirements.txt
>> python-keystoneclient in stable/juno was capped at <=1.1.0, and 1.1.0 is
>> the version tagged for the stable branch. When you create a review in
>> stable/juno it installs python-keystoneclient and now the system has got a
>> version like 1.1.0.post1, which is>1.1.0, so now python-keystoneclient
>> doesn't match the requirements and swift-proxy fails to start (swift-proxy
>> is very good at catching this problem for whatever reason). The cap should
>> have been <1.2.0 so that we can propose patches and also make fix releases
>> (1.1.1, 1.1.2, etc.).[3]
>> [3] https://review.openstack.org/#/c/172718/
> Approved.

we have the same issue for ceilometerclient for both icehouse[1] and juno[2], i put up requirement patches for each [3][4]

[1] https://review.openstack.org/#/c/173085/
[2] https://review.openstack.org/#/c/173086/
[3] https://review.openstack.org/#/c/173149/
[4] https://review.openstack.org/#/c/173148/

>> I tried to recap all of the clients but that didn't pass Jenkins, probably
>> because one or more clients didn't use semver correctly and have
>> requirements updates in a micro release.[4]
>> [4] https://review.openstack.org/#/c/172719/
> Did you literally update them all, or only the ones that looked like
> they might be wrong? It looks like those caps came from the cap.py
> script in the repository, which makes me wonder if we were just too
> aggressive with defining what the cap should be.

don't know about others but full disclosure, we didn't use SEMVER correctly. :\



More information about the OpenStack-dev mailing list