[Yahoo-eng-team] [Bug 1837995] Re: "Unexpected API Error" when use "openstack usage show" command
** Changed in: nova/ussuri Status: Fix Committed => Fix Released -- 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/1837995 Title: "Unexpected API Error" when use "openstack usage show" command Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) train series: New Status in OpenStack Compute (nova) ussuri series: Fix Released Status in OpenStack Compute (nova) victoria series: Fix Released Bug description: Description === For a non-admin project, if you have instance launched. And try to query the usage information on GUI by clicking Overview or on CLI: openstack usage show I will got "Error: Unable to retrieve usage information." on GUI. and the following ERROR for CLI output: $ openstack usage show Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Steps to reproduce == Execute "openstack usage show" command Or click Project - Compute - Overview button on the GUI. Expected result === No Error report and the usage information shown Actual result = Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Environment === 1. Exact version of OpenStack you are running. Openstack Stein on CentOS7 $ rpm -qa | grep nova openstack-nova-api-19.0.1-1.el7.noarch puppet-nova-14.4.0-1.el7.noarch python2-nova-19.0.1-1.el7.noarch openstack-nova-conductor-19.0.1-1.el7.noarch openstack-nova-novncproxy-19.0.1-1.el7.noarch openstack-nova-migration-19.0.1-1.el7.noarch openstack-nova-common-19.0.1-1.el7.noarch openstack-nova-scheduler-19.0.1-1.el7.noarch openstack-nova-console-19.0.1-1.el7.noarch python2-novaclient-13.0.1-1.el7.noarch openstack-nova-placement-api-19.0.1-1.el7.noarch openstack-nova-compute-19.0.1-1.el7.noarch 2. Which hypervisor did you use? Libvirt + KVM $ rpm -qa | grep kvm qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 $ rpm -qa | grep libvirt libvirt-gconfig-1.0.0-1.el7.x86_64 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64 libvirt-4.5.0-10.el7_6.12.x86_64 libvirt-glib-1.0.0-1.el7.x86_64 libvirt-daemon-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64 libvirt-python-4.5.0-1.el7.x86_64 libvirt-libs-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64 libvirt-client-4.5.0-10.el7_6.12.x86_64 libvirt-gobject-1.0.0-1.el7.x86_64 Logs & Configs == nova-api.log 2019-07-26 16:12:53.967 8673 INFO nova.osapi_compute.wsgi.server [req-69d7df76-7dd9-4d42-8eeb-347ef1c9d0a5 f887cc44f21043dca85438d74a47d68d 0d47cfd5b9c94a5790fa4472e576cba6 - default default] c5f::e2 "GET /v2.1/0d47cfd5b9c94a5790fa4472e576cba6/servers/detail?all_tenants=True=2019-07-26T08%3A07%3A55.280119%2B00%3A00 HTTP/1.1" status: 200 len: 413 time: 0.0639658 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi [req-cbea9542-ecce-42fd-b660-fc5f996ea3c3 1e45ea9a7d5647a6a938c2ac027822f2 85dd8936d21b46a8878ed59678c7ad9a - default default] Unexpected exception in API method: OrphanedObjectError: Cannot call obj_load_attr on orphaned Instance object 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 671, in wrapped 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi return f(*args,
[Yahoo-eng-team] [Bug 1837995] Re: "Unexpected API Error" when use "openstack usage show" command
** Changed in: nova/victoria Status: Fix Committed => Fix Released -- 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/1837995 Title: "Unexpected API Error" when use "openstack usage show" command Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) train series: New Status in OpenStack Compute (nova) ussuri series: New Status in OpenStack Compute (nova) victoria series: Fix Released Bug description: Description === For a non-admin project, if you have instance launched. And try to query the usage information on GUI by clicking Overview or on CLI: openstack usage show I will got "Error: Unable to retrieve usage information." on GUI. and the following ERROR for CLI output: $ openstack usage show Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Steps to reproduce == Execute "openstack usage show" command Or click Project - Compute - Overview button on the GUI. Expected result === No Error report and the usage information shown Actual result = Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Environment === 1. Exact version of OpenStack you are running. Openstack Stein on CentOS7 $ rpm -qa | grep nova openstack-nova-api-19.0.1-1.el7.noarch puppet-nova-14.4.0-1.el7.noarch python2-nova-19.0.1-1.el7.noarch openstack-nova-conductor-19.0.1-1.el7.noarch openstack-nova-novncproxy-19.0.1-1.el7.noarch openstack-nova-migration-19.0.1-1.el7.noarch openstack-nova-common-19.0.1-1.el7.noarch openstack-nova-scheduler-19.0.1-1.el7.noarch openstack-nova-console-19.0.1-1.el7.noarch python2-novaclient-13.0.1-1.el7.noarch openstack-nova-placement-api-19.0.1-1.el7.noarch openstack-nova-compute-19.0.1-1.el7.noarch 2. Which hypervisor did you use? Libvirt + KVM $ rpm -qa | grep kvm qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 $ rpm -qa | grep libvirt libvirt-gconfig-1.0.0-1.el7.x86_64 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64 libvirt-4.5.0-10.el7_6.12.x86_64 libvirt-glib-1.0.0-1.el7.x86_64 libvirt-daemon-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64 libvirt-python-4.5.0-1.el7.x86_64 libvirt-libs-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64 libvirt-client-4.5.0-10.el7_6.12.x86_64 libvirt-gobject-1.0.0-1.el7.x86_64 Logs & Configs == nova-api.log 2019-07-26 16:12:53.967 8673 INFO nova.osapi_compute.wsgi.server [req-69d7df76-7dd9-4d42-8eeb-347ef1c9d0a5 f887cc44f21043dca85438d74a47d68d 0d47cfd5b9c94a5790fa4472e576cba6 - default default] c5f::e2 "GET /v2.1/0d47cfd5b9c94a5790fa4472e576cba6/servers/detail?all_tenants=True=2019-07-26T08%3A07%3A55.280119%2B00%3A00 HTTP/1.1" status: 200 len: 413 time: 0.0639658 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi [req-cbea9542-ecce-42fd-b660-fc5f996ea3c3 1e45ea9a7d5647a6a938c2ac027822f2 85dd8936d21b46a8878ed59678c7ad9a - default default] Unexpected exception in API method: OrphanedObjectError: Cannot call obj_load_attr on orphaned Instance object 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 671, in wrapped 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi return f(*args,
[Yahoo-eng-team] [Bug 1837995] Re: "Unexpected API Error" when use "openstack usage show" command
** Also affects: nova/victoria Importance: Undecided Status: New ** Also affects: nova/train Importance: Undecided Status: New ** Also affects: nova/ussuri 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/1837995 Title: "Unexpected API Error" when use "openstack usage show" command Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) train series: New Status in OpenStack Compute (nova) ussuri series: New Status in OpenStack Compute (nova) victoria series: New Bug description: Description === For a non-admin project, if you have instance launched. And try to query the usage information on GUI by clicking Overview or on CLI: openstack usage show I will got "Error: Unable to retrieve usage information." on GUI. and the following ERROR for CLI output: $ openstack usage show Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Steps to reproduce == Execute "openstack usage show" command Or click Project - Compute - Overview button on the GUI. Expected result === No Error report and the usage information shown Actual result = Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Environment === 1. Exact version of OpenStack you are running. Openstack Stein on CentOS7 $ rpm -qa | grep nova openstack-nova-api-19.0.1-1.el7.noarch puppet-nova-14.4.0-1.el7.noarch python2-nova-19.0.1-1.el7.noarch openstack-nova-conductor-19.0.1-1.el7.noarch openstack-nova-novncproxy-19.0.1-1.el7.noarch openstack-nova-migration-19.0.1-1.el7.noarch openstack-nova-common-19.0.1-1.el7.noarch openstack-nova-scheduler-19.0.1-1.el7.noarch openstack-nova-console-19.0.1-1.el7.noarch python2-novaclient-13.0.1-1.el7.noarch openstack-nova-placement-api-19.0.1-1.el7.noarch openstack-nova-compute-19.0.1-1.el7.noarch 2. Which hypervisor did you use? Libvirt + KVM $ rpm -qa | grep kvm qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 $ rpm -qa | grep libvirt libvirt-gconfig-1.0.0-1.el7.x86_64 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64 libvirt-4.5.0-10.el7_6.12.x86_64 libvirt-glib-1.0.0-1.el7.x86_64 libvirt-daemon-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64 libvirt-python-4.5.0-1.el7.x86_64 libvirt-libs-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64 libvirt-client-4.5.0-10.el7_6.12.x86_64 libvirt-gobject-1.0.0-1.el7.x86_64 Logs & Configs == nova-api.log 2019-07-26 16:12:53.967 8673 INFO nova.osapi_compute.wsgi.server [req-69d7df76-7dd9-4d42-8eeb-347ef1c9d0a5 f887cc44f21043dca85438d74a47d68d 0d47cfd5b9c94a5790fa4472e576cba6 - default default] c5f::e2 "GET /v2.1/0d47cfd5b9c94a5790fa4472e576cba6/servers/detail?all_tenants=True=2019-07-26T08%3A07%3A55.280119%2B00%3A00 HTTP/1.1" status: 200 len: 413 time: 0.0639658 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi [req-cbea9542-ecce-42fd-b660-fc5f996ea3c3 1e45ea9a7d5647a6a938c2ac027822f2 85dd8936d21b46a8878ed59678c7ad9a - default default] Unexpected exception in API method: OrphanedObjectError: Cannot call obj_load_attr on orphaned Instance object 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File
[Yahoo-eng-team] [Bug 1837995] Re: "Unexpected API Error" when use "openstack usage show" command
Trying out a WIP patch here: https://review.opendev.org/c/openstack/nova/+/773834 ** Changed in: nova Status: Invalid => In Progress ** Changed in: nova Assignee: (unassigned) => melanie witt (melwitt) -- 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/1837995 Title: "Unexpected API Error" when use "openstack usage show" command Status in OpenStack Compute (nova): In Progress Bug description: Description === For a non-admin project, if you have instance launched. And try to query the usage information on GUI by clicking Overview or on CLI: openstack usage show I will got "Error: Unable to retrieve usage information." on GUI. and the following ERROR for CLI output: $ openstack usage show Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Steps to reproduce == Execute "openstack usage show" command Or click Project - Compute - Overview button on the GUI. Expected result === No Error report and the usage information shown Actual result = Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Environment === 1. Exact version of OpenStack you are running. Openstack Stein on CentOS7 $ rpm -qa | grep nova openstack-nova-api-19.0.1-1.el7.noarch puppet-nova-14.4.0-1.el7.noarch python2-nova-19.0.1-1.el7.noarch openstack-nova-conductor-19.0.1-1.el7.noarch openstack-nova-novncproxy-19.0.1-1.el7.noarch openstack-nova-migration-19.0.1-1.el7.noarch openstack-nova-common-19.0.1-1.el7.noarch openstack-nova-scheduler-19.0.1-1.el7.noarch openstack-nova-console-19.0.1-1.el7.noarch python2-novaclient-13.0.1-1.el7.noarch openstack-nova-placement-api-19.0.1-1.el7.noarch openstack-nova-compute-19.0.1-1.el7.noarch 2. Which hypervisor did you use? Libvirt + KVM $ rpm -qa | grep kvm qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 $ rpm -qa | grep libvirt libvirt-gconfig-1.0.0-1.el7.x86_64 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64 libvirt-4.5.0-10.el7_6.12.x86_64 libvirt-glib-1.0.0-1.el7.x86_64 libvirt-daemon-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64 libvirt-python-4.5.0-1.el7.x86_64 libvirt-libs-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64 libvirt-client-4.5.0-10.el7_6.12.x86_64 libvirt-gobject-1.0.0-1.el7.x86_64 Logs & Configs == nova-api.log 2019-07-26 16:12:53.967 8673 INFO nova.osapi_compute.wsgi.server [req-69d7df76-7dd9-4d42-8eeb-347ef1c9d0a5 f887cc44f21043dca85438d74a47d68d 0d47cfd5b9c94a5790fa4472e576cba6 - default default] c5f::e2 "GET /v2.1/0d47cfd5b9c94a5790fa4472e576cba6/servers/detail?all_tenants=True=2019-07-26T08%3A07%3A55.280119%2B00%3A00 HTTP/1.1" status: 200 len: 413 time: 0.0639658 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi [req-cbea9542-ecce-42fd-b660-fc5f996ea3c3 1e45ea9a7d5647a6a938c2ac027822f2 85dd8936d21b46a8878ed59678c7ad9a - default default] Unexpected exception in API method: OrphanedObjectError: Cannot call obj_load_attr on orphaned Instance object 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 671, in wrapped 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2019-07-26 16:12:57.211 8682
[Yahoo-eng-team] [Bug 1837995] Re: "Unexpected API Error" when use "openstack usage show" command
** Changed in: nova Status: Incomplete => Invalid -- 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/1837995 Title: "Unexpected API Error" when use "openstack usage show" command Status in OpenStack Compute (nova): Invalid Bug description: Description === For a non-admin project, if you have instance launched. And try to query the usage information on GUI by clicking Overview or on CLI: openstack usage show I will got "Error: Unable to retrieve usage information." on GUI. and the following ERROR for CLI output: $ openstack usage show Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Steps to reproduce == Execute "openstack usage show" command Or click Project - Compute - Overview button on the GUI. Expected result === No Error report and the usage information shown Actual result = Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-cbea9542-ecce-42fd-b660-fc5f996ea3c3) Environment === 1. Exact version of OpenStack you are running. Openstack Stein on CentOS7 $ rpm -qa | grep nova openstack-nova-api-19.0.1-1.el7.noarch puppet-nova-14.4.0-1.el7.noarch python2-nova-19.0.1-1.el7.noarch openstack-nova-conductor-19.0.1-1.el7.noarch openstack-nova-novncproxy-19.0.1-1.el7.noarch openstack-nova-migration-19.0.1-1.el7.noarch openstack-nova-common-19.0.1-1.el7.noarch openstack-nova-scheduler-19.0.1-1.el7.noarch openstack-nova-console-19.0.1-1.el7.noarch python2-novaclient-13.0.1-1.el7.noarch openstack-nova-placement-api-19.0.1-1.el7.noarch openstack-nova-compute-19.0.1-1.el7.noarch 2. Which hypervisor did you use? Libvirt + KVM $ rpm -qa | grep kvm qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 $ rpm -qa | grep libvirt libvirt-gconfig-1.0.0-1.el7.x86_64 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-interface-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-secret-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-kvm-4.5.0-10.el7_6.12.x86_64 libvirt-bash-completion-4.5.0-10.el7_6.12.x86_64 libvirt-4.5.0-10.el7_6.12.x86_64 libvirt-glib-1.0.0-1.el7.x86_64 libvirt-daemon-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-config-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-4.5.0-10.el7_6.12.x86_64 libvirt-python-4.5.0-1.el7.x86_64 libvirt-libs-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-network-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.12.x86_64 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.12.x86_64 libvirt-client-4.5.0-10.el7_6.12.x86_64 libvirt-gobject-1.0.0-1.el7.x86_64 Logs & Configs == nova-api.log 2019-07-26 16:12:53.967 8673 INFO nova.osapi_compute.wsgi.server [req-69d7df76-7dd9-4d42-8eeb-347ef1c9d0a5 f887cc44f21043dca85438d74a47d68d 0d47cfd5b9c94a5790fa4472e576cba6 - default default] c5f::e2 "GET /v2.1/0d47cfd5b9c94a5790fa4472e576cba6/servers/detail?all_tenants=True=2019-07-26T08%3A07%3A55.280119%2B00%3A00 HTTP/1.1" status: 200 len: 413 time: 0.0639658 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi [req-cbea9542-ecce-42fd-b660-fc5f996ea3c3 1e45ea9a7d5647a6a938c2ac027822f2 85dd8936d21b46a8878ed59678c7ad9a - default default] Unexpected exception in API method: OrphanedObjectError: Cannot call obj_load_attr on orphaned Instance object 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 671, in wrapped 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2019-07-26 16:12:57.211 8682 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/simple_tenant_usage.py", line 291, in show 2019-07-26
