yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #33210
[Bug 1422476] Re: floating ip scheduled to wrong router
** Also affects: neutron/juno
Importance: Undecided
Status: New
** Changed in: neutron/juno
Status: New => Fix Committed
** Changed in: neutron/juno
Importance: Undecided => Medium
** Changed in: neutron/juno
Assignee: (unassigned) => Akihiro Motoki (amotoki)
** Tags removed: in-stable-juno juno-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1422476
Title:
floating ip scheduled to wrong router
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in neutron juno series:
Fix Committed
Status in OpenStack Security Advisories:
Won't Fix
Bug description:
I have a tenant network, two external networks, two routers (each one
has gateway set to one of the external networks, and one port on the
tenant network) and floating ip's on each external network.
In icehouse, this worked fine. the floating ip for each network was
attached to the correct router. After upgrading to RDO Juno, I'm
seeing both sets of floating ip's getting assigned to the same router:
[root@cloud ~]# ip netns exec qrouter-209158a6-ee00-405f-b929-7cb386460d94 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
44: qr-ffaaacc1-06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:5c:e1:58 brd ff:ff:ff:ff:ff:ff
inet 192.168.127.1/24 brd 192.168.127.255 scope global qr-ffaaacc1-06
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe5c:e158/64 scope link
valid_lft forever preferred_lft forever
53: qg-1a260edc-41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:81:dc:f7 brd ff:ff:ff:ff:ff:ff
inet 192.101.107.185/25 brd 192.101.107.255 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.168.122.179/32 brd 192.168.122.179 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.168.122.128/32 brd 192.168.122.128 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.101.107.171/32 brd 192.101.107.171 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.101.107.181/32 brd 192.101.107.181 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.101.107.180/32 brd 192.101.107.180 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet 192.101.107.179/32 brd 192.101.107.179 scope global qg-1a260edc-41
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe81:dcf7/64 scope link
valid_lft forever preferred_lft forever
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1422476/+subscriptions