Public bug reported: Description =========== in Ocata-stable release version, after creating a vm in error state due to some reason, the quota_usages table will increase corresponding. While after delete the error vm, the quota_usages table would not change. If large numbers of error vm have been created, it's exhaust all resources.
Steps to reproduce ================== A chronological list of steps which will bring off the issue you noticed: create vm in error state due to limits of ram for example. check the quota_usages table delete the error vm checek the quota_usages table Expected result =============== the resources should be released after deleting the error vm. Actual result ============= resources does not release after deleting the error vm. Environment =========== 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ root@controller:/var/log/nova# dpkg -l | grep nova ii nova-api 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - API frontend ii nova-common 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-conductor 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - conductor service ii nova-consoleauth 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - Console Authenticator ii nova-novncproxy 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - NoVNC proxy ii nova-placement-api 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - placement API frontend ii nova-scheduler 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - virtual machine scheduler ii python-nova 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute Python libraries ii python-novaclient 2:7.1.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - Python 2.7 root@compute1:/home/user# dpkg -l | grep nova ii nova-common 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-compute 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node base ii nova-compute-kvm 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node (KVM) ii nova-compute-libvirt 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node libvirt support ii python-nova 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute Python libraries ii python-novaclient 2:7.1.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - Python 2.7 2. Which hypervisor did you use? (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...) What's the version of that? 2. Which storage type did you use? (For example: Ceph, LVM, GPFS, ...) What's the version of that? 3. Which networking type did you use? Neutron with OpenVSwitch Logs & Configs ============== The tool *sosreport* has support for some OpenStack projects. It's worth having a look at it. For example, if you want to collect the logs of a compute node you would execute: $ sudo sosreport -o openstack_nova --batch on that compute node. Attach the logs to this bug report. Please consider that these logs need to be collected in "DEBUG" mode. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1698259 Title: delete vm in error state cannot release the resource Status in OpenStack Compute (nova): New Bug description: Description =========== in Ocata-stable release version, after creating a vm in error state due to some reason, the quota_usages table will increase corresponding. While after delete the error vm, the quota_usages table would not change. If large numbers of error vm have been created, it's exhaust all resources. Steps to reproduce ================== A chronological list of steps which will bring off the issue you noticed: create vm in error state due to limits of ram for example. check the quota_usages table delete the error vm checek the quota_usages table Expected result =============== the resources should be released after deleting the error vm. Actual result ============= resources does not release after deleting the error vm. Environment =========== 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ root@controller:/var/log/nova# dpkg -l | grep nova ii nova-api 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - API frontend ii nova-common 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-conductor 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - conductor service ii nova-consoleauth 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - Console Authenticator ii nova-novncproxy 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - NoVNC proxy ii nova-placement-api 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - placement API frontend ii nova-scheduler 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - virtual machine scheduler ii python-nova 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute Python libraries ii python-novaclient 2:7.1.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - Python 2.7 root@compute1:/home/user# dpkg -l | grep nova ii nova-common 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-compute 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node base ii nova-compute-kvm 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node (KVM) ii nova-compute-libvirt 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute - compute node libvirt support ii python-nova 2:15.0.0-0ubuntu1~cloud0 all OpenStack Compute Python libraries ii python-novaclient 2:7.1.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - Python 2.7 2. Which hypervisor did you use? (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...) What's the version of that? 2. Which storage type did you use? (For example: Ceph, LVM, GPFS, ...) What's the version of that? 3. Which networking type did you use? Neutron with OpenVSwitch Logs & Configs ============== The tool *sosreport* has support for some OpenStack projects. It's worth having a look at it. For example, if you want to collect the logs of a compute node you would execute: $ sudo sosreport -o openstack_nova --batch on that compute node. Attach the logs to this bug report. Please consider that these logs need to be collected in "DEBUG" mode. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698259/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
