I've asked Mark McClain to tag a new release before *specifically* because we're going to hit the issue. The issue is in both master and stable/havana. Latest client releases were tagged by Mark, but since he seems to be busy these days, I think someone should step in and tag and release a new client ASAP, otherwise we leave stable/havana neutron broken for indefinite time. It's unacceptable. /Ihar
----- Original Message ----- > 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 > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
