yahoo-eng-team team mailing list archive

[venkata anil <anil.venkata@xxxxxxxxxxxx>]

** Changed in: networking-ovn
     Assignee: (unassigned) => venkata anil (anil-venkata)

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

** Changed in: neutron
     Assignee: (unassigned) => venkata anil (anil-venkata)

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

Title:
  Router namespace missing after neutron L3 agent restarted

Status in networking-ovn:
  New
Status in neutron:
  New

Bug description:
  After restarting the neutron L3 agent, the router namespace is
  deleted, but not recreated.

  Recreate scenario:
  1) Deploy OVN with the neutron L3 agent instead of the native L3 support.
  2) Follow http://docs.openstack.org/developer/networking-ovn/testing.html to test the deployment.
  3) Setup a floating IP address for one of the VMs.
  4) Check the namespaces.

  $ sudo ip netns
  qrouter-d4937a95-9742-4ed3-a8a6-7eccb622837d
  qdhcp-4ed85305-259e-4f62-a7a4-32aed191c546

  5) SSH to the VM via the floating IP address.

  $ ssh -i id_rsa_demo cirros@172.24.4.3
  $ exit
  Connection to 172.24.4.3 closed.

  6) Use screen to stop and then restart q-l3.
  7) Check the namespaces.

  $ sudo ip netns
  qdhcp-4ed85305-259e-4f62-a7a4-32aed191c546

  8) Disassociate the floating IP address from the VM.  This seems to receate the namespace.  It's possible that other operations would do the same.
  9) Check the namespaces.

  $ sudo ip netns
  qrouter-d4937a95-9742-4ed3-a8a6-7eccb622837d
  qdhcp-4ed85305-259e-4f62-a7a4-32aed191c546

  10) Associate the floating IP address to the VM again and connectivity
  is restored to the VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1541859/+subscriptions