We hit this in a fresh Bifrost deployment this morning, and, so far as I can tell, it's going to affect every project that uses oslo.messaging (eg, Nova, Keystone, Ironic, ...) downstream, if someone installs that project with "pip install -r requirements.txt", because oslo.messaging specifies "amqp>=1.4.0".
It does not affect project gates because the gate environment uses upper-constraints, which currently pins "amqp===1.4.9".
Related bug report: https:/ /bugs.launchpad .net/nova/ +bug/1586979
We hit this in a fresh Bifrost deployment this morning, and, so far as I can tell, it's going to affect every project that uses oslo.messaging (eg, Nova, Keystone, Ironic, ...) downstream, if someone installs that project with "pip install -r requirements.txt", because oslo.messaging specifies "amqp>=1.4.0".
It does not affect project gates because the gate environment uses upper-constraints, which currently pins "amqp===1.4.9".