yahoo-eng-team team mailing list archive

[sean mooney <smooney@xxxxxxxxxx>]

this might be somthing that could be added to the exsiting 
neutron-ovs-cleanup script
that is generated by this entry point https://github.com/openstack/neutron/blob/master/setup.cfg#L49
and impmeneted here https://github.com/openstack/neutron/blob/master/neutron/cmd/ovs_cleanup.py

but this should not live in nova.

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Won't Fix

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

Title:
  you can end up in a state where qvo* interfaces aren't owned by ovs
  which results in a dangling connection

Status in neutron:
  New
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  While upgrading to rocky, we ended up with a broken openvswitch
  infrastructure and moved back to the old openvswitch.

  We ended up with new machines working, old machines didn't and it took
  a while to realize that we had qvo* interfaces that not only wasn't
  plugged but also wasn't owned by ovs-system - basically the virtual
  equivalent of forgetting to plug in the cable ;)

  This was quickly addressed by running this bash-ism on all nodes:
  for x in `ip a |grep qvo |grep @qvb |grep -v ovs-system | awk '{ print $2 '}` ; do y=${x%%"@"*} && ip link delete $y ; done ; docker restart nova_compute

  However, nova could pretty easily sanity check this =)

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