Managed OpenStack
Latest
VM went into paused state after trying to stop it
Problem
VM went into the paused state after trying to stop it.
Cannot perform any action on the VM.
Environment
Platform9 Managed OpenStack - v5.4.0 and Higher
Cause
From ostackhost logs, it seems VM power off failed and then it went into paused state:
2022-09-07 10:37:17.990 INFO nova.image.pf9_glance [req-b8fefaa1-4f54-xxx-xxx-bb7815f99b9c abc@xyz.com service] Fetched new image-cluster endpoint list: ['http://192.168.30.33:9292', 'http://192.168.30.38:9292']
2022-09-07 10:37:20.808 INFO nova.compute.manager [req-b8fefaa1-4f54-xxx-xxx-bb7815f99b9c abc@xyz.com service] [instance: afcb39b4-xxxx-xxxx-xxxx-f130cb97c5e5] Successfully reverted task state from powering-off on failure for instance.
2022-09-07 10:37:21.364 ERROR oslo_messaging.rpc.server [req-b8fefaa1-4f54-xxx-xxx-bb7815f99b9c abc@xyz.com service] Exception during message handling: libvirt.libvirtError: Requested operation is not valid: domain is not running
2022-09-07 10:37:21.364 TRACE oslo_messaging.rpc.server Traceback (most recent call last):
...
2022-09-07 10:37:21.364 TRACE oslo_messaging.rpc.server if ret == -1: raise libvirtError ('virDomainShutdown() failed', dom=self)
Resolution
Login to the host holding the VM and check the current status:
$ sudo virsh list|grep <VM_ID>
Resume the paused VM using below command:
$ sudo virsh resume <VM_ID>
Additional Information
https://docs.openstack.org/mitaka/user-guide/cli_stop_ and_start_ an_instance.html
Last updated on
Was this page helpful?
Frequently Asked Questions
Solution
How To
Internal Only
Templates
Powered by
