yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #27106
[Bug 1413510] [NEW] floating IP no longer works after migrate a router from legacy to distributed.
Public bug reported:
Create a legacy router (--distribute=False) and attach private and
public subnet to the router.
boot a VM using private subnet, create a floating IP and associate the
floating IP to VM's port.
Update the router to distributed=True. The VM can no longer reach
external network.
This is because the floating IP is still on qg device of qrouter
namespace. qg device should be removed from qrouter namespace after
router is changed to distributed.
** Affects: neutron
Importance: Undecided
Assignee: Xu Han Peng (xuhanp)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Xu Han Peng (xuhanp)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1413510
Title:
floating IP no longer works after migrate a router from legacy to
distributed.
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
Create a legacy router (--distribute=False) and attach private and
public subnet to the router.
boot a VM using private subnet, create a floating IP and associate the
floating IP to VM's port.
Update the router to distributed=True. The VM can no longer reach
external network.
This is because the floating IP is still on qg device of qrouter
namespace. qg device should be removed from qrouter namespace after
router is changed to distributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1413510/+subscriptions
Follow ups
References