This is only in 4.0 in Bionic and not in earlier nor in later releases.
Thanks buguldey for reporting back on this.
The change only adds/removes a bug from being reported.
So the reported error will change, but it should not change the actual overall
behavior.
I haven't seen a rather clear "if you do this, that happens" on this bug to
consider the fix important yet. Furthermore I haven't seen other reports on the
same in all the time.
Therefore i'm considering stability (not changing it until we know more) over a
fix even we know the commit/revert now.
Since this was reported coming up in ceilometer, are there openstack
people out there that see this more often and can back this as being a
common problem?
** Also affects: libvirt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: libvirt (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770295
Title:
ceilometer compute cannot collection memory.usage meter for all vm in
one compute node
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1770295/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
