yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Seen here:

http://logs.openstack.org/54/232554/17/check/gate-grenade-dsvm-
multinode/dcd1e94/logs/old/screen-n-api.txt.gz?level=INFO#_2015-12-03_09_47_51_258

https://github.com/openstack/nova/blob/89dd62aabf62175724e0e05765c9759cd9160263/nova/virt/libvirt/host.py#L654

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

** Changed in: nova
       Status: Opinion => Confirmed

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

** Tags added: libvirt low-hanging-fruit

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

Title:
  Nova is leaking libvirt internal ids on some Instance Not Found errors

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  Nova from master in the gate.

  libvirt is incorrectly using InstanceNotFound as an internal
  exception, but handing it libvirt internal ids instead of an openstack
  uuid or ec2id. This means it jumps up through the stack and back to
  the user, giving errors over http like Instance instance-000000a not
  found. This is both an information leak, and useless bit of
  information for the user to figure out what's going on.

  libvirt should use an internal exception instead.

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