Re: [openstack-dev] [TripleO][Neutron] Urgent python-neutronclient release needed
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
Re: [openstack-dev] [TripleO][Neutron] Urgent python-neutronclient release needed
And for those interested in details: the issue was triggered by 3799efe792700e773c40cc42c265eee09230 in master (15a912b1ca3c24ba8851b8b77d6de8027e120d78 in stable/havana). The required fix in neutronclient that should be released ASAP is: 02baef46968b816ac544b037297273ff6a4e8e1b. I'm going to update both global and neutron requirements.txt right after we get a new release at PyPI. - Original Message - 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO][Neutron] Urgent python-neutronclient release needed
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
