Bug 1469084 - Instances don't start automatically after a compute node reboot [NEEDINFO]
Instances don't start automatically after a compute node reboot
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
7.0 (Kilo)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Eoghan Glynn
Joe H. Rahme
: ZStream
Depends On:
  Show dependency treegraph
Reported: 2017-07-10 07:30 EDT by Sergii Mykhailushko
Modified: 2017-08-29 13:32 EDT (History)
15 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-21 10:29:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
dansmith: needinfo? (smykhail)

Attachments (Terms of Use)

  None (edit)
Description Sergii Mykhailushko 2017-07-10 07:30:01 EDT
Description of problem:
We have two compute nodes with the same configuration. One of them fails to start guest instances after hypervisor restart.

The following KCS was been created for this issue:

Though it works in our reproducer environment, it still can't fix the issue on customer's site.

Steps to Reproduce:
1. Start an instance on hypervisor
2. Reboot nova node

Actual results:
All instances are in shutdown state

Expected results:
Instances (with running state before hypervisor reboot) should be resumed

Additional info:
This has been tested in our reproducer env with different libvirt-guests/nova configuration options with only one combination leading to have guests resuming after nova reboot. But this doesn't seem to work in customer env

resume_guests_state_on_host_boot=true in nova.conf
libvirt-guests.service enabled
ON_BOOT=ignore, ON_SHUTDOWN=shutdown in /etc/sysconfig/libvirt-guests

Note You need to log in before you can comment on or make changes to this bug.