https://bugs.launchpad.net/neutron/+bug/1280941

I haven't done a chapter-and-verse trace of what happened, but it
looks like a latent bug in the neutronclient lib was tickled by some
neutron change, fixed in neutronclient, and then neutron started using
the feature without bumping requirements.txt (as is needed for all
hard dependencies).

As a result, TripleO clouds currently break, because we're meeting
requirements.txt, but requirements.txt is faulty.

If someone with Neutron can-do-relase acls can do a release asap I
think that would be the best fix. Alternatively, we could hunt down
and backout whatever Neutron change tickles this (but a client release
seems best overall to me).

-Rob

-- 
Robert Collins <rbtcoll...@hp.com>
Distinguished Technologist
HP Converged Cloud

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to