Bug 1441349

+++ This bug was initially created as a clone of Bug #1390846 +++

Description of problem:

ceilometer-polling: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid <UUID> is output in /var/log/messages.

Version-Release number of selected component (if applicable):

OSP 8.0

How reproducible:

100%

Steps to Reproduce:

One possible reproduce method:

1. Create an instance
2. virsh undefine <domain>
3. Wait for 10 minutes and check /var/log/messages

Actual results:

The above message will be output

Expected results:

Can we add some exception handling when some instance has been deleted ?


Additional info:

--- Additional comment from Mehdi ABAAKOUK on 2016-11-18 15:17:55 CET ---

If the domain is destroyed in libvirt but not in nova, that the expected message.

--- Additional comment from Chen on 2016-11-18 16:44:23 CET ---

Hi Mehdi,

Thank you for your reply.

Is there any chance that we can have a better handling so that we can forbid this message from outputting in the logs ? Polling a non-existent instance has no meaning so can we make this error message silent ?

Best Regards,
Chen

--- Additional comment from Mehdi ABAAKOUK on 2016-11-21 14:10:24 CET ---

If you want the message to disappear, you must delete the instance in nova.
For ceilometer, the instance should exists because nova tell us it exists.
If something is wrong/outofsync between libvirt and nova and we can't really known why from a Ceilometer PoV, so we print a message. We can't do more.

--- Additional comment from Chen on 2017-03-14 07:29:58 CET ---

Hi Mehdi,

Could you please confirm our RHSOP8 is being affected by the following bugs ?

https://bugs.launchpad.net/ceilometer/+bug/1656166
https://review.openstack.org/#/c/333129/

Best Regards,
Chen

--- Additional comment from Mehdi ABAAKOUK on 2017-03-14 09:31:22 CET ---

Good finding,

Yes, the caching mechanism have been introduced in RHOSP 8, and have this issue.

But the fix can't be backported alone and depends on another feature introduced in RHOSP9: https://review.openstack.org/#/c/284322/

These also introduces two new configuration options.

The bug also affects RHOS 9 and 10.

--- Additional comment from Chen on 2017-03-16 07:22:59 CET ---

Hi Mehdi,

Thank you for your reply.

So just to clarify, is this issue

1. impossible to be backported to OSP8 due to https://review.openstack.org/#/c/284322/

2. can be backported to OSP8 despite of https://review.openstack.org/#/c/284322/
 but it would take more time

Which one is correct ?

Best Regards,
Chen

--- Additional comment from Mehdi ABAAKOUK on 2017-03-16 08:49:48 CET ---

It's option 2, also these changes have to be backported on OSP8, OSP9 and OSP10 to ensure future upgrade will not introduce regression again.