Le 17/02/2016 13:43, Henry Gessau a écrit :
And it looks like eventlet 0.18.3 breaks neutron:
https://bugs.launchpad.net/neutron/+bug/1546506

2 releases, 2 regressions in OpenStack. Should we cap eventlet version? The requirement bot can produce patches to update eventlet, patches which would run integration tests using Nova, Keystone, Neutron on the new eventlet version.

eventlet 0.18.2 broke OpenStack Keystone and OpenStack Nova
https://github.com/eventlet/eventlet/issues/296
https://github.com/eventlet/eventlet/issues/299
https://review.openstack.org/#/c/278147/
https://bugs.launchpad.net/nova/+bug/1544801

eventlet 0.18.3 broke OpenStack Neutron
https://github.com/eventlet/eventlet/issues/301
https://bugs.launchpad.net/neutron/+bug/1546506

FYI eventlet 0.18.0 broke WSGI servers:
https://github.com/eventlet/eventlet/issues/295

It was followed quickly by eventlet 0.18.2 to fix this issue.

Sadly, it looks like bugfix releases of eventlet don't include a single bugfix, but include also other changes. For example, 0.18.3 fixed the bug #296 but introduced "wsgi: TCP_NODELAY enabled by default" optimization.

IMHO the problem is not the release manager of eventlet, but more the lack of tests on eventlet, especially on OpenStack services.

Current "Continious Delivery"-like with gates do detect bugs, yeah, but also block a lot of developers when the gates are broken. It doesn't seem trivial to investigate and fix eventlet issues.

Victor

__________________________________________________________________________
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

Reply via email to