yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1493768] [NEW] Cannot configure router HA port when L2 agent is down while creating HA router

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Artur Korzeniewski <artur.korzeniewski@xxxxxxxxx>
Date: Wed, 09 Sep 2015 09:51:16 -0000
Reply-to: Bug 1493768 <1493768@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

The situation I have encounter in Liberty-3 devstack.

When creating HA router on network nodes with dead L2 agent (ovs), the
HA port cannot be properly configured on that node after starting the L2
agent - the L2 agent is treating the HA port as dead and is blocking all
the traffic on that port in OVS flow.

The only way to recover from that situation is to delete the HA router
and then create a new one.

Steps to reproduce:
1. Have 2 network nodes: turn off L2 agent on one of them.
2. Create HA router.
3. Check for ha- interfaces, one of them will not be configured in OVS.
4. Start L2 agent
5. In OVS flows the HA port will be blocked, and it will have assign VLAN 4095.
There is no way of recover from that situation, beside deleting the HA router.

** 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/1493768

Title:
  Cannot configure router HA port when L2 agent is down while creating
  HA router

Status in neutron:
  New

Bug description:
  The situation I have encounter in Liberty-3 devstack.

  When creating HA router on network nodes with dead L2 agent (ovs), the
  HA port cannot be properly configured on that node after starting the
  L2 agent - the L2 agent is treating the HA port as dead and is
  blocking all the traffic on that port in OVS flow.

  The only way to recover from that situation is to delete the HA router
  and then create a new one.

  Steps to reproduce:
  1. Have 2 network nodes: turn off L2 agent on one of them.
  2. Create HA router.
  3. Check for ha- interfaces, one of them will not be configured in OVS.
  4. Start L2 agent
  5. In OVS flows the HA port will be blocked, and it will have assign VLAN 4095.
  There is no way of recover from that situation, beside deleting the HA router.

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