yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Medium
         Status: Triaged


** Tags: 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