[Yahoo-eng-team] [Bug 1868889] [NEW] instance turned to "error" state after reboot compute node

Public bug reported: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --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

[Yahoo-eng-team] [Bug 1868890] [NEW] instance turned to "error" state after reboot compute node

Public bug reported: Description === The instance turned to "error" state after reboot compute node. And I tried the "nova reset-state --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

[Yahoo-eng-team] [Bug 1863755] [NEW] default vcpus_used and memory_mb_used for ironic baremetal node was not 0

Public bug reported: Description === When a baremetal node enrolled to ironic, nova whould create one hypervisor for the baremeatl node.By default the values of vcpus_used and memory_mb_used was not 0, even though no instance scheduled to this baremeatl nodes. Steps to reproduce

[Yahoo-eng-team] [Bug 1860312] [NEW] compute service failed to delete

Public bug reported: Description === I deployed openstack with openstack-helm on kubernetes.When one of the nova-compute service(driver=ironic replica of the deployment is 1) breakdown.It may be scheduled to another node by kubernetes.When I try to delete the old compute service(status