Suspended instances cannot resume after hypervisor reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Rafi Khardalian |
Bug Description
Suspended instances cannot resume after hypervisor reboot using the libvirt driver. The method to reproduce the problem is simple:
1. Create a new tenant (VLAN manager network model should be configured) and launch an instance within this tenant.
2. Suspend the instance.
3. Reboot the hypervisor on which the suspended instance rests. Assume for the sake of discussion it comes back up without a problem and restarts the compute service.
4. Resume the instance. It will fail.
The reason it fails is that we're expecting the physical system to be in a state which it is not. The networking is not in place (bridge, VLAN, iptables rules, etc.), nor are any block device connections. The resume() method calls _create_domain(), which will not rebuild any of these dependencies. We should call _create_
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
no longer affects: | nova/folsom |
Fix proposed to branch: master /review. openstack. org/13251
Review: https:/