yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #08481
[Bug 1202362] Re: quantum-ovs-cleanup removes system devices that OVS is still looking for
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1202362
Title:
quantum-ovs-cleanup removes system devices that OVS is still looking
for
Status in OpenStack Neutron (virtual network service):
Expired
Bug description:
After rebooting a machine, and running the quantum-ovs-cleanup utility
in Grizzly (which seems to be the recommended practice--however only
recommended by way of the Launchpad bug thread in which it was
created), the script seems to delete the qg-/qr-/tap system devices. I
did not instruct it to do so via the quantum_ports=False setting.
This behavior almost sounds normal, however even after ensuring that
the L3 and DHCP agents start after this cleanup script finishes, I get
hundreds of errors in the OVS vswitchd log indicating it can't find
these interfaces (mostly gq-/qr-). Additionally, none of my Quantum
networks are functional at that point.
From this point forward, nothing recovers; I continue seeing the same
vswitchd log errors (to the point that it rate limits them), I presume
since the agents are requesting status on them so often.
Let me know what log/console output is helpful here and I'll be happy
to paste or attach.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1202362/+subscriptions