** Changed in: quantum/folsom
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1091605
Title:
Internal interfaces defined via OVS are not brought up properly after
a reboot
Status in OpenStack Quantum (virtual network service):
Fix Released
Status in quantum folsom series:
Fix Released
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
necessary.
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:
https://bugs.launchpad.net/quantum/+bug/1091605/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
