Huh, so this actually reproducible by just using `nova stop $instance ; nova start $instance` after the host reboot. I missed this when initially creating the bug as I assumed it was due to the state the host was in after resume_guests_state_on_host_boot attempted and failed to run the instance.
IMHO resume_guests_state_on_host_boot is just broken and not tested anywhere, I'd like to re-purpose this bug to tackle the simpler stop;start use case that should be fixed by the following change:
Huh, so this actually reproducible by just using `nova stop $instance ; nova start $instance` after the host reboot. I missed this when initially creating the bug as I assumed it was due to the state the host was in after resume_ guests_ state_on_ host_boot attempted and failed to run the instance.
IMHO resume_ guests_ state_on_ host_boot is just broken and not tested anywhere, I'd like to re-purpose this bug to tackle the simpler stop;start use case that should be fixed by the following change:
https:/ /review. openstack. org/#/c/ 400384/