yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03814
[Bug 1183276] Re: Misleading ERROR message relating to instances not found in database
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => havana-2
--
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/1183276
Title:
Misleading ERROR message relating to instances not found in database
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
We are seeing the following error message in the nova-compute logs:
Instance <ID> found in the hypervisor, but not in the database
Upon investigation we found that the instance is running on the
hypervisor and correctly entered in the database.
I've tracked this down to a function in the compute manager _get_instances_on_driver. This method is called periodically from
_running_deleted_instances (and possibly from other places). _get_instances_on_driver calls instance_get_all_by_filters and, in this case, the filters are set to retrieve deleted instances on the current host. The list of instances retrieved is compared to the list of instances currently running on the hypervisor. Any instances on the host but not listed in the return from the db query are logged in the above error format, however this means instances which are perfectly healthy are getting logged simply because they are not set to deleted.
This results in an error message for every instance on the host being
logged each time the periodic task happens. I think we need to remove
the log message in this case as it can't know what filters have been
specified and so can't provide useful information and just causes
noise for anyone monitoring errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1183276/+subscriptions