** No longer affects: nova/folsom -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1052696
Title: Suspended instances cannot resume after hypervisor reboot Status in OpenStack Compute (Nova): Fix Released 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_domain_and_network() instead, so that we eliminate any assumptions about the state of the hypervisor. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1052696/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
