Comment 9 for bug 1587356

Well, it is impossible for me to provide a method to reproduce this, as of today, October 2019 (3 years and almost a half later) this is not present anymore for new instances

For the sake of clarity: our DB is not mangled by means of any external tooling, so this was something caused by nova. I reckon that this is not present anymore for new instances (but we still do have several in the DB that are raising errors).

I would close the ticket as invalid and I will fix manually the DB instances.