I ran into this issue the other day on an internal project. There are probably two errors. One in Quantum and one in eventlet masking as a SQLAlchemy bug.
For the Quantum bug: Try temporarily wrapping the code inside of the transaction in a try/except. In the except, call LOG.exception() and raise the exception again. In you know how to trigger the bug even better, otherwise you'll have to wait until it bubbles up again. The eventlet error is here: https://bitbucket.org/eventlet/eventlet/issue/129/exception-info-clearing-is-problematic-and mark On Mar 7, 2013, at 7:34 PM, Aaron Rosen <[email protected]> wrote: > Hey Guys, > > I've been running into this exception every now and then the past day > and was wondering if anyone had any ideas why? > > http://codepad.org/Zpjj7U12 > > Thanks, > > Aaron > > -- > Mailing list: https://launchpad.net/~quantum-core > Post to : [email protected] > Unsubscribe : https://launchpad.net/~quantum-core > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
