Is this bug repeatable? The cleaned column not existing in the downgrade means that it wasn't created in the upgrade. I don't see how that could be happening unless something really unexpected is wrong.

I'd like to point out that once again, the requirements.txt do not decide what kind of package we hold in the distribution, and therefore, this type of argumentation is completely invalid. I'm having issues with unit tests in Sid, which used to run SQLA 0.8, and which now has 0.9. In both cases, it fails. I really would like to fix these.

As you see, Chuck is having the same issue that I have in Debian in Ubuntu.

In talking with Thomas it sounds like there is a problem with using latest sqlalchemy-migrate and sqlalchemy > 0.7.99 with nova, I do remember Dan Prince needing to fix something in nova when we tried updating to migrate 0.8.2 for sqla 0.8 support, we'd have to go back and find that change and backport it to stable/havana. It was pretty trivial from what I remember, something about the migration test code putting a cap on migrate/sqlalchemy for a now-invalid reason.