[Bug 1758411] Re: [SRU] Revert fix for bug 1752838 regression

Edward Hope-Morley edward.hope-morley at canonical.com
Fri Mar 23 18:49:39 UTC 2018


** Description changed:

  [Impact]
  
  The fix for the following bug was found to cause a regression/race with
  neutron-ovs-cleanup and neutron-openvswitch-agent where ports/flows get
  deleted and do not get restored.
  
  https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1752838
  
  [Test Case]
- Deploy OpenStack
- Create instance
- juju ssh nova-compute/0
- virsh list #ensure instance lives on this machine else ssh to another compute node
- sudo ovs-vsctl show
- sudo restart openvswitch-switch
- sudo ovs-vsctl show # Ensure ports haven't changed
+ * Deploy OpenStack Mitaka with one compute, one gateway and gre overlay
+ * Create instance on gre overlay network
+ * Add FIP to instance
+ * Start a ping to FIP
+ * juju ssh nova-compute/0
+ * Check 'ovs-ofctl dump-flows br-tun' and observe table=20 egress flows for qdhcp and qrouter
+ * systemctl restart openvswitch-switch
+ * Check that flows re-added to br-tun
+ * Check that ping still running
  
  [Regression Potential]
  
  There should be none as long as the code is reverted to what it was
  before the SRU for 1752838.

** Description changed:

  [Impact]
  
  The fix for the following bug was found to cause a regression/race with
  neutron-ovs-cleanup and neutron-openvswitch-agent where ports/flows get
  deleted and do not get restored.
  
  https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1752838
  
  [Test Case]
  * Deploy OpenStack Mitaka with one compute, one gateway and gre overlay
  * Create instance on gre overlay network
  * Add FIP to instance
  * Start a ping to FIP
  * juju ssh nova-compute/0
  * Check 'ovs-ofctl dump-flows br-tun' and observe table=20 egress flows for qdhcp and qrouter
  * systemctl restart openvswitch-switch
- * Check that flows re-added to br-tun
+ * Check that flows re-added to br-tun (this takes a few seconds for neutron-openvswitch-agent to re-add them)
  * Check that ping still running
  
  [Regression Potential]
  
  There should be none as long as the code is reverted to what it was
  before the SRU for 1752838.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1758411

Title:
  [SRU] Revert fix for bug 1752838 regression

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in Ubuntu Cloud Archive pike series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in neutron package in Ubuntu:
  Triaged
Status in neutron source package in Xenial:
  Triaged
Status in neutron source package in Artful:
  Triaged
Status in neutron source package in Bionic:
  Triaged

Bug description:
  [Impact]

  The fix for the following bug was found to cause a regression/race
  with neutron-ovs-cleanup and neutron-openvswitch-agent where
  ports/flows get deleted and do not get restored.

  https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1752838

  [Test Case]
  * Deploy OpenStack Mitaka with one compute, one gateway and gre overlay
  * Create instance on gre overlay network
  * Add FIP to instance
  * Start a ping to FIP
  * juju ssh nova-compute/0
  * Check 'ovs-ofctl dump-flows br-tun' and observe table=20 egress flows for qdhcp and qrouter
  * systemctl restart openvswitch-switch
  * Check that flows re-added to br-tun (this takes a few seconds for neutron-openvswitch-agent to re-add them)
  * Check that ping still running

  [Regression Potential]

  There should be none as long as the code is reverted to what it was
  before the SRU for 1752838.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1758411/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list