yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Public bug reported:

We trace the exception when hitting InstanceInfoCacheNotFound while
refreshing the network info_cache, which is a normal case if the
instance is being deleted from under us:

http://logs.openstack.org/30/167830/14/experimental/check-tempest-dsvm-
neutron-aiopcpu-
full/86090e2/logs/screen-n-cpu.txt.gz?level=TRACE#_2015-04-01_21_14_29_370

So we shouldn't trace when we hit InstanceInfoCacheNotFound.

** Affects: nova
     Importance: Low
     Assignee: Matt Riedemann (mriedem)
         Status: Triaged


** Tags: network

** Changed in: nova
   Importance: Undecided => Low

** Changed in: nova
       Status: New => Triaged

** Changed in: nova
     Assignee: (unassigned) => Matt Riedemann (mriedem)

-- 
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/1441361

Title:
  Don't trace on InstanceInfoCacheNotFound when refreshing network
  info_cache

Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  We trace the exception when hitting InstanceInfoCacheNotFound while
  refreshing the network info_cache, which is a normal case if the
  instance is being deleted from under us:

  http://logs.openstack.org/30/167830/14/experimental/check-tempest-
  dsvm-neutron-aiopcpu-
  full/86090e2/logs/screen-n-cpu.txt.gz?level=TRACE#_2015-04-01_21_14_29_370

  So we shouldn't trace when we hit InstanceInfoCacheNotFound.

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