yahoo-eng-team team mailing list archive

[Brian Haley <1696796@xxxxxxxxxxxxxxxxxx>]

This is an invalid configuration, a DVR router cannot be hosted on a
legacy node.

To do this correctly, you should first migrate the router(s) to
distributed=False, then change agent_mode=legacy.

** Changed in: neutron
       Status: Incomplete => Invalid

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

Title:
  No fip connectivity after switch to legacy mode from dvr_snat

Status in neutron:
  Invalid

Bug description:
  Setup: all-in-one devstack, agent_mode=dvr_snat in
  /etc/neutron/l3_agent.ini

  Create a security group with allowed icmp, boot a vm in default
  private network with this security group, assign a floating ip, make
  sure the vm can be pinged by floating ip (sample env setup script -
  http://paste.openstack.org/show/612405/)

  Change agent_mode=legacy, restart neutron server and l3-agent.

  The vm won't be reachable by floating ip and l3 agent log will be full
  of traces of the kind http://paste.openstack.org/show/612006/

  Router update with distributed=False returns connectivity so I believe
  the problem is with processing the distributed router in legacy mode.

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