yahoo-eng-team team mailing list archive

[Stephen Ma <stephen.ma@xxxxxx>]

Public bug reported:

When using DVR, the fg device in a compute is needed to access VMs on a
compute node.  If for any reason the fg- device is deleted.  users will
not be able access the VMs on the compute node.

On a single node system where the L3-agent is running in 'dvr-snat'
mode, a VM is booted up and assigned a floating-ip.  The VM is pingable
using the floating IP.  Now I go into the fip namespace and delete the
fg device using the command "ovs-vsctl del-port br-ex fg-ccbd7bcb-75. "
Now the the VM can no longer be pinged.

Then another VM is booted up and it is also assigned a Floating IP.  The
new VM is not pingable either.

The L3-agent log shows it reported that it cannot find fg-ccbd7bcb-75
when setting up the qrouter and fip namespaces for the new floating IP.
But it didn't not go and re-create the fg- device.

Given that this is a deliberate act to cause the cloud  to fail, the
L3-agent could have gone ahead and re-create the fg device to make it
more fault tolerant.

The problem can be reproduced with the latest neutron code.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  L3-agent not recreating missing fg- device

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When using DVR, the fg device in a compute is needed to access VMs on
  a compute node.  If for any reason the fg- device is deleted.  users
  will not be able access the VMs on the compute node.

  On a single node system where the L3-agent is running in 'dvr-snat'
  mode, a VM is booted up and assigned a floating-ip.  The VM is
  pingable using the floating IP.  Now I go into the fip namespace and
  delete the fg device using the command "ovs-vsctl del-port br-ex fg-
  ccbd7bcb-75. "   Now the the VM can no longer be pinged.

  Then another VM is booted up and it is also assigned a Floating IP.
  The new VM is not pingable either.

  The L3-agent log shows it reported that it cannot find fg-ccbd7bcb-75
  when setting up the qrouter and fip namespaces for the new floating
  IP.  But it didn't not go and re-create the fg- device.

  Given that this is a deliberate act to cause the cloud  to fail, the
  L3-agent could have gone ahead and re-create the fg device to make it
  more fault tolerant.

  The problem can be reproduced with the latest neutron code.

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