Updating Power_state in the DB to match the hypervisor

The error message is as follows:

2017-10-02 22:42:02.944 80378 INFO Nova.compute.manager [req-347dcc06-13cb-4ced-a10d-b21bf4427430-----] [Instance:ec 21B955-8D9C-4C42-AB33-CE5D32D6BA61] During _sync_instance_power_state the DB power_state (1) does not match the Vm_power_ State from the hypervisor (4). Updating Power_state in the DB to match the hypervisor. 2017-10-02 22:42:03.009 80378 WARNING Nova.compute.manager [req-347dcc06-13cb-4ced-a10d-b21bf4427430-----] [instance : Ec21b955-8d9c-4c42-ab33-ce5d32d6ba61] Instance shutdown by itself. Calling the Stop API. Current vm_state:active, current Task_state:none, original DB power_state:1, current VM Power_state:4 2017-10-02 22:42:03.116 80378 INFO Nova.compute.manager [req-347dcc06-13cb-4ced-a10d-b21bf4427430-----] [Instance:ec 21B955-8D9C-4C42-AB33-CE5D32D6BA61] Instance is already powered off with the hypervisor when stop is called. 2017-10-02 22:42:03.171 80378 INFO nova.virt.libvirt.driver [req-347dcc06-13cb-4ced-a10d-b21bf4427430-----] [Instanc E:EC21B955-8D9C-4C42-AB33-CE5D32D6BA61] Instance already shutdown.

Workaround:

Modifying a configuration file/etc/nova/nova.conf

Sync_power_state_interval=-1

This is the management level used to detect the power state of the virtual machine parameters, resulting in the compute node above the virtual host inexplicably shutdown.

Reference Document: http://www-01.ibm.com/support/docview.wss?uid=nas8N1020669

This article is from the "Endless Bitter Companion" blog, please be sure to keep this source http://linuxshow.blog.51cto.com/1572053/1979377

Updating Power_state in the DB to match the hypervisor