As far as I remember, this was happening when Nova instances failed to start due to insufficient resources (it was a small test environment). Intentionally causing a quota validation might reproduce the issue, assuming it wasn't fixed already.
As far as I remember, this was happening when Nova instances failed to start due to insufficient resources (it was a small test environment). Intentionally causing a quota validation might reproduce the issue, assuming it wasn't fixed already.