Fix proposed to branch: master
Review: https://review.openstack.org/518520
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719770
Title:
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) => Edward Hope-Morley (hopem)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719770
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
Hi @afreiberger, i've run a test using our charms and Xenial Mitaka and
here are the results - http://pastebin.ubuntu.com/25879833/
A few points for clarification:
When you do juju remove-unit nova-compute/0 the charm is not performing
any cleanup at all i.e. it will not notify the cloud
I'm still working on reproducing. While attempting reproduction, I had
an environment where I had 3 hosts, dummy charms on each for ubuntu,
then added nova-compute to 3. Removed nova-compute unit from the third
host, and still saw stats for it in hypervisor-stats. There may be some
cleanup
Marking 'Incomplete' for now until we get a reproducer figured out.
** Changed in: nova (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nova (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719770
Title:
I can not reproduce the problem, I see SQL has used
'compute_nodes.deleted = 0' to filter deleted services as the following
debug info shows (mitaka).
(Pdb)
(Pdb) 'SELECT count(compute_nodes.id) AS count_1, sum(compute_nodes.vcpus) AS
sum_1, sum(compute_nodes.memory_mb) AS sum_2,
In models.py, both in Mitaka and in master, I've found that the relation
between ComputeNode and Service is using the following join in the
Service context:
primaryjoin='and_(Service.host == Instance.host,'
'Service.binary == "nova-compute",'
This code has had some significant refactoring since mitaka; so its
possible this only impacts older openstack releases.
Either way, this is not a charm problem but a Nova issue AFAICT -
raising distro task.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed
10 matches
Mail list logo
