Bug 1469084 - Instances don't start automatically after a compute node reboot
Summary: Instances don't start automatically after a compute node reboot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 7.0 (Kilo)
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Eoghan Glynn
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-10 11:30 UTC by Sergii Mykhailushko
Modified: 2023-09-14 04:00 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-21 14:29:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sergii Mykhailushko 2017-07-10 11:30:01 UTC
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:
https://access.redhat.com/solutions/2979711

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
~~~

Comment 11 Red Hat Bugzilla 2023-09-14 04:00:50 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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