> It didn't seem like a good fit for tracking technical issues we're > encountering - I created another one here [2] with a glance/pycrypto > issue I noticed in upstream gate. > > [1]: https://review.rdoproject.org/etherpad/p/ocata-release-preparation > [2]: https://etherpad.openstack.org/p/rdo-ocata-release-issues Updated the etherpad, this is not pycrypto, but probably related to openssl-1.0.1e-60.el7_3.1 CentOS7 update which was pushed today? Cheers, Alan

On Wed, Feb 22, 2017 at 7:30 AM, Alan Pevec <apevec(a)redhat.com&gt; wrote: >> It didn't seem like a good fit for tracking technical issues we're >> encountering - I created another one here [2] with a glance/pycrypto >> issue I noticed in upstream gate. >> >> [1]: https://review.rdoproject.org/etherpad/p/ocata-release-preparation >> [2]: https://etherpad.openstack.org/p/rdo-ocata-release-issues > > Updated the etherpad, this is not pycrypto, but probably related to > openssl-1.0.1e-60.el7_3.1 CentOS7 update which was pushed today? > I've just tested that the issue has been introduced by python2-cryptography-1.7.2-1.el7.x86_64. It doesn't appear when downgrading to previous python2-cryptography-1.3.1-3.el7.x86_64. I'd say we should revert to pervious 1.3.1. Note that version 1.7.2 is in upstream u-c so the issue may be specific to RDO package or SSL termination may not be tested in upstream glance gate. I'm testing it with cryptography from pypi.

> Cheers, > Alan