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. __________________________________________________________________________ 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
