yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

** Also affects: nova/newton
   Importance: Undecided
       Status: New

** Changed in: nova/newton
       Status: New => Confirmed

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

** Tags added: libvirt

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

Title:
  libvirt driver leaves interface residue after failed start

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) newton series:
  Confirmed

Bug description:
  When the libvirt driver fails to start a VM due to reasons other than
  neutron plug timeout, it leaves interfaces on the system from the vif
  plugging. If a subsequent delete is performed and completes
  successfully, these will be removed. However, in cases where
  connectivity is preventing a normal delete, a local delete will be
  performed at the api level and the interfaces will remain.

  In at least one real world situation I have observed, a script was
  creating test instances which were failing and leaving residue. After
  the residue interface count reached about 6,000 on the system, VM
  creates started failing with "Argument list too long" as libvirt was
  choking on enumerating the interfaces it had left behind.

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