Comment 10 for bug 1278591

Not really, this was the second case I encountered it in a very long time.
My guess is that it could be reproduced in reasonable time with moderate network traffic and a bunch of lxc-start/stop. After a while it should happen.

Anyway reading the commit message it's very probable, that this commit will fix this issue.