On 04/04/2017 09:19 AM, Jay S Bryant wrote:
Monty,
I agree with your approach. Think we should not break other projects
with a change like this and the answer thus far has been to just patch
each project individually to work around the issues introduced by
eventlet. So, I support this approach and think Sean would as well.
To follow up with everyone - dims and I spent a bit of time this morning
testing combinations of things, and it seems that master of eventlet
actually also does not fix things - there are some issues that will just
need to be figured out.
The suggested path forward at the moment is to pull designate out of the
requirements-sync process so it can stay pinned at 0.19 while the issues
are sorted out. A patch to bump designate back to 0.20.1 can accompany
the patch to fix it for 0.20.1 - and can be done as people have time,
rather than in a rush.
On 4/4/2017 8:33 AM, Monty Taylor wrote:
Hey all,
We recently increased the version of eventlet we're using. The bump
was driven by python3.5 enablement for oslo.messaging, which is a
great thing to have exist. However, it has hard-broken designate - and
not just the docs builds like happened for other projects.
There is a patch that has landed to upstream eventlet that will fix
the designate issues, but it is not yet released.
I'd like to propose we revert the U-C bump and block 0.20 in our
requirements. This hamstrings the 3.5 enablement a bit, but it
unbreaks designate, and I'd argue that we need to prioritize not
breaking services in cases like this. (also, because designate is
broken, openstack-ansible has gate issues, and shade had gate issues
until we removed designate from our gate config which was extremely
sad making)
Sean McGinnis already proposed a patch to revert the bump:
https://review.openstack.org/#/c/448104/
which I think we should restore, then modify it to also include a
requirements block. As soon as 0.21 is released, we can upgrade to
that and get 3.5 for oslo.messaging back on track.
Thoughts?
Monty
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
