Public bug reported:

Ceilometer was causing resources to have a huge amount of revisions on Gnocchi
(1000+), because the compute pollsters were constantly pushing outdated
attributes. This can happen when users (as an example), update the name of VMs.
The name is not updated in the VM's XML that is stored in the KVM host.
This causes the Ceilometer compute pollster to constantly push outdated 
attributes
that trigger resource revisions on Gnocchi (if we have other pollsters pushing 
the right
attribute value that is gathered from OpenStack API).

We are using OpenStack Rocky, and Nova version is 18.0.1.

** Affects: ceilometer
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Also affects: ceilometer
   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/1853048

Title:
  Nova not updating VM's XML in KVM

Status in Ceilometer:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  Ceilometer was causing resources to have a huge amount of revisions on Gnocchi
  (1000+), because the compute pollsters were constantly pushing outdated
  attributes. This can happen when users (as an example), update the name of 
VMs.
  The name is not updated in the VM's XML that is stored in the KVM host.
  This causes the Ceilometer compute pollster to constantly push outdated 
attributes
  that trigger resource revisions on Gnocchi (if we have other pollsters 
pushing the right
  attribute value that is gathered from OpenStack API).

  We are using OpenStack Rocky, and Nova version is 18.0.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1853048/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to