Comment 1 for bug 1040942

Thanks for the report!

I've just reproduced this by:

  1) Set reservation_expire=10 and periodic_interval=20 in nova.conf

  2) Do 'nova secgroup-create foo bar' twice (see #1043765)

  3) Confirm that we have a lingering reservation from that failure by running 'select * from reservations where deleted=0;' against the nova DB

Wait a while and, sure enough, I see the same exception you do.

By the way, whatever caused the quota reservation to leak is a bug too. It would be good to track that bug down. A good start is to look at the 'resource' column of the leaked reservations.