yahoo-eng-team team mailing list archive

[Peter Sabaini <peter.sabaini@xxxxxxxxxxxxx>]

Public bug reported:

Due to an apparent communication issue between neutron-openvswitch-agent
and openvswitch  we were in a situation where we had linux veth devices
set up for a given instance (eg. tapXXX, qvbXXX) but were missing
corresponding ovs ports and iptables rules.

In this situation we had to manually delete veth devices and restart
nova-compute and neutron-openvswitch-agent to get openvswitch ports and
iptables rules recreated.

It would be more robust if neutron and openvswitch would automatically
detect missing objects and synchronize their view of which devices and
ports should be present

Versions: 
Openstack Mitaka on Ubuntu xenial
neutron: 2:8.4.0-0ubuntu5  
openvswitch-switch 2.5.2-0ubuntu0.16.04.1

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: canonical-bootstack

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1720163

Title:
  Openvswitch ports not getting recreated

Status in neutron:
  New

Bug description:
  Due to an apparent communication issue between neutron-openvswitch-
  agent and openvswitch  we were in a situation where we had linux veth
  devices set up for a given instance (eg. tapXXX, qvbXXX) but were
  missing corresponding ovs ports and iptables rules.

  In this situation we had to manually delete veth devices and restart
  nova-compute and neutron-openvswitch-agent to get openvswitch ports
  and iptables rules recreated.

  It would be more robust if neutron and openvswitch would automatically
  detect missing objects and synchronize their view of which devices and
  ports should be present

  Versions: 
  Openstack Mitaka on Ubuntu xenial
  neutron: 2:8.4.0-0ubuntu5  
  openvswitch-switch 2.5.2-0ubuntu0.16.04.1

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