There is a well-known bug in the Paramiko SSH library that causes
these Exceptions:
SSHException: Error connecting via ssh: PID check failed. RNG must be
re-initialized after fork(). Hint: Try Random.atfork()
This bug has been fixed in Paramiko, and therefore we should require
the newer version for Cinder drivers that use Paramiko to function
properly.
Change-Id: I0844db1011f8b5c0e771b0e99a83027a13b6ea75
Fixes: bug 1150720
oslo.config has now been released to PyPI in time for Grizzly RC1 so
we can switch to using it directly.
Change-Id: I655f831718ae5f4e25e941ee206fe195214a9a91
0.7.10 has been released and is compatible with 0.7.x. Instead
of pinning to 0.7.9, simply pin to 0.7.x to avoid SQLAlchemy 0.8
Unfortuantely '<0.8' matches '0.8.0b2', which is what we don't want.
Therefore pinning it to '<=0.7.99' instead.
Change-Id: I14eef50b5a423140421c6e8fe0a5242c2f676fa4
This patch updates tools/pip-requires to use the python-quantumclient 2.2
It also limits the version to <3.0.0 to prevent breaking something accidently
when 3.0.0 is released.
Fixes bug 1152695
Change-Id: I90e5118798ef2fca3b8b07acefe13336479d524f
This is the result of running a script (see next commit) which just
takes all of the pip-requires and test-requires files from our
projects and makes a consolidated list from them.
I had to do some manual cleanup to remove duplicates. This means it's
not a complete list since some of the requires are actually incompatible
like keystoneclient or sqlalchemy.
So, this still isn't sufficient to build a complete PyPI mirror from
yet, but it is closer to the current requirements set and doesn't
artificially pin us to specific versions.
We need to come back around and cap the version ranges according to
each upstream's policy for changing their release numbers when they
make incompatible changes:
http://lists.openstack.org/pipermail/openstack-dev/2013-March/006331.html
Change-Id: I616aa67eee6c559906b2a7a2322686e0c6d846da
