Comment 16 for bug 1457404

Today's update: we gave it another try on 3 different environments with nova-network/FlatDHCPManager and haven't managed to reproduce this issue.

We asked Alexander A. to try to reproduce it on the original environment. The *only* repro was right after Alexander reverted the snapshot. After that, we were unable to reproduce this issue again by booting/deleting multiple instances concurrently.

Right now, my understanding is that this is some kind of an edge case, that can be seen only *right after* a snapshot revert, and thus, PI team see Jenkins failures periodically.

Whatever it actually is, the issue only affects particular fixed IPs, until their leases expire, so its influence on the environment is *very* limited (not even saying we can't reproduce it without snapshotting/reverting an environment).

Workaround on nova-network side would be ugly and error-prone. I suggest PI team just decrease lease expire time if you see it in your Jenkins jobs again.