[openstack-dev] [cinder] cinder is broken until someone fixes the forking code

Doug Hellmann doug at doughellmann.com
Wed Mar 11 18:36:35 UTC 2015

On Wed, Mar 11, 2015, at 01:47 PM, Mike Bayer wrote:
> Hello Cinder -
> I’d like to note that for issue
> https://bugs.launchpad.net/oslo.db/+bug/1417018, no solution that
> actually
> solves the problem for Cinder is scheduled to be committed anywhere. The
> patch I proposed for oslo.db is on hold, and the patch proposed for
> oslo.incubator in the service code will not fix this issue for Cinder, it
> will only make it fail harder and faster.
> I’ve taken myself off as the assignee on this issue, as someone on the
> Cinder team should really propose the best fix of all which is to call
> engine.dispose() when first entering a new child fork. Related issues are
> already being reported, such as
> https://bugs.launchpad.net/cinder/+bug/1430859. Right now Cinder is very
> unreliable on startup and this should be considered a critical issue.

That service code is actually from the Oslo incubator, so we should fix
it there. If we can always call engine.dispose(), then let's put that
into the incubated module and see how it works in cinder (submit the
patch to the incubator, then update cinder's copy and submit a patch
with Depends-On set to point to the patch to the incubator so the copy
in cinder won't be updated until we land the fix in the incubator).


> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list