[Bug 1719770] Change abandoned on nova (master)
OpenStack Infra
1719770 at bugs.launchpad.net
Wed Nov 15 13:34:18 UTC 2017
Change abandoned by Edward Hope-Morley (edward.hope-morley at canonical.com) on branch: master
Review: https://review.openstack.org/518520
Reason: This already fixed as part of bug 1692397 and backported as far as Newton. I need this fix for Mitaka so will look into SRU for ubuntu packages.
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1719770
Title:
hypervisor stats aggregates resources from deleted and existing
services if they share the same hostname
Status in OpenStack nova-compute charm:
Invalid
Status in OpenStack Compute (nova):
Invalid
Status in nova package in Ubuntu:
Invalid
Bug description:
In an environment with 592 physical threads (lscpu |grep '^CPU.s' and
openstack hypervisor show -f value -c vcpus both show correct counts)
I am seeing 712 vcpus. (likely also seeing inflated memory_mb and
other stats due to the issue.)
Querying the nova services DB table, I see:
http://pastebin.ubuntu.com/25624553/
It appears that of the 6 machines showing deleted in the services
table, only one is showing as disabled.
Digging through the nova/db/sqlalchemy/api.py code, it appears that
there are filters on the hypervisor stats for Service.disabled ==
false() and Service.binary == 'nova-compute', but I don't see it
filtering for deleted == 0.
I'm not exactly certain of the timeline of my uninstall and reinstall
of the nova-compute units on the 6 x 24vcpu servers happened (see
*-ST-{1,2} nova-compute services) that caused this behavior of the
services not getting disabled, but nova api for hypervisor stats might
be well served to filter out deleted services as well as disabled
services, or if a deleted service should never not be disabled, nova
service-delete should also set the disabled flag for the service.
These services and compute_nodes do not show up in openstack
hypervisor list.
Site is running up-to-date Xenial/Mitaka on openstack-charmers 17.02.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1719770/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list