[Bug 1091605] Re: Internal interfaces defined via OVS are not brought up properly after a reboot

James Page james.page at ubuntu.com
Sat Feb 25 06:16:14 UTC 2017

quantum is no longer found in any supported Ubuntu release

** Changed in: quantum (Ubuntu)
       Status: Incomplete => Won't Fix

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to quantum in Ubuntu.

  Internal interfaces defined via OVS are not brought up properly after
  a reboot

Status in neutron:
  Fix Released
Status in neutron folsom series:
  Fix Released
Status in quantum package in Ubuntu:
  Won't Fix

Bug description:
  The L3 agents and DHCP agents both define internal (qg-, qr-, tap-)
  ports via OVS.  In both cases, the agents call plug() to configure and
  bring the device up if it does not exist.  If the device does exist,
  however, the agents neither call plug nor do they ensure the link is
  up (OVS ensures that the devices survive a reboot but does not ensure
  that they are brought up on boot).

  The responsibility for bringing devices up should probably remain in
  quantum/agent/linux/interface.py, so a suggested implementation would
  be delegating the device existence check to the driver's plug()
  method, which could then ensure that the device was brought up if

  This bug reveals a hole in our current testing strategy.   Most
  developers presumably work on devstack rather than installed code.
  Since devstack agents don't survive a reboot, most developers would
  never have the chance to validate whether a quantum agent node still
  works after a reboot.  Documenting use-cases that need to be tested
  (e.g. quantum agent nodes need to work properly after a reboot) is a
  good first step - is this currently captured somewhere or can we find
  a place to do so?

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list