I think comment #8 is right. Looks like this is implemented with commit [1] and should work through [2] as requested in the original description.
If there are any questions left, feel free to contact me (markus_z) in the IRC channel #openstack-nova References: [1] https://git.openstack.org/cgit/openstack/nova/commit/?id=ba4946d0d3c73e5d9f67f42203d103bf98563458 [2] https://github.com/openstack/nova/blob/af8d078d97a4ce7be48fa20572164f0cc79cbd21/nova/compute/manager.py#L1177-L1185 ** Changed in: nova Status: Confirmed => Fix Released -- 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/1169769 Title: start guests on host reboot Status in OpenStack Compute (nova): Fix Released Bug description: Story: A host has a power fluctuation and reboots. The VM state in the DB is Active. The VM state in the driver is Shutoff. The sysadmin goes in to xenserver and xe starts all the instances. nova.compute.manager.Manager._run_image_cache_manager_pass runs, it finds that the DB vs driver states are incompatible, it says the driver is kind, and updates the DB now all the VMs that sysadmin started are down again. ----- Work around: After host reboots, shut down the compute service, start the VMs, start the compute service ----- Background: There used to be an option: 'start_guests_on_host_boot' The trouble with it was that it started VMs, even if the DB state was suspended. It was removed here: https://review.openstack.org/#/c/16698/ ------ Suggested fix: Re-add a nova.conf option: 'start_guests_on_host_boot' But make it submit to the DB state, and only start a guest if it is labeled as running in the DB. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1169769/+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
