[Bug 1719770] Re: hypervisor stats issue after charm removal if nova-compute service not disabled first
Edward Hope-Morley
edward.hope-morley at canonical.com
Fri Nov 3 15:49:20 UTC 2017
Bug Confirmed - http://paste.ubuntu.com/25880271/
Deploying nova-compute to a host that previously had a nova-compute
deployed to it (i.e. hostname recycled) will result in nova hypervisor
stats reporting stats from both the deleted and active entries of that
service.
In terms of the nova-compute charm i think the topic of how it behaves
when removing units has come up before i.e. that it should somehow mark
the service/host as deleted when removing a unit of nova-compute. The
problem with doing this is that the compute service would need to be
provided with admin credentials since it no longer has direct access to
the db. This has been previously raised and the bug is still pending -
https://bugs.launchpad.net/charms/+source/nova-compute/+bug/1317560.
** Changed in: nova (Ubuntu)
Status: Incomplete => Confirmed
--
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 issue after charm removal if nova-compute service not
disabled first
Status in OpenStack nova-compute charm:
Invalid
Status in nova package in Ubuntu:
Confirmed
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