Comment 9 for bug 1398128

If we really wanted to band-aid this, we could enhance devstack's resource polling to also wait for mem/cpu/gb to reach an expected state, though I wonder if there's something happening in Nova that's causing this. This seems like a new issue we're hitting so perhaps something has changed recently on that front?