instance turned to "error" state after reboot compute node

Bug #1868889 reported by tanghang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

Description
===========
The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state <id> --active" command, the instance turned into active state. But, when I login the compute node and use "virsh list" command, there are no instance on the compute node.Then, I ran the "openstack server stop" and "openstack server start" command.After that, the server recovered.

Steps to reproduce
==================
1. Create a instance
2. Confirm the compute node the instance running on
3. Reboot the compute node

===============
After the execution of the steps above, what should have
happened if the issue wasn't present?

the server shoud migrated to other compute nodes or should recover automatically after the conpute node reboot.
Actual result
=============
the server turned into "error" state

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/
       18.2.3

2. Which hypervisor did you use?
   Libvirt + KVM

2. Which storage type did you use?
   Ceph

3. Which networking type did you use?
   Neutron with OpenVSwitch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.