yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #50410
[Bug 1469322] Re: Associating a floatingip with a dual stack port requires the fixed-address to be specified
** Also affects: neutron/kilo
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/1469322
Title:
Associating a floatingip with a dual stack port requires the fixed-
address to be specified
Status in neutron:
Fix Released
Status in neutron kilo series:
New
Bug description:
Associating a floatingip with a dual stack port fails unless the IPv4
address is specified with the fixed-ip-address parameter. Presently
when a user attempts to associate a floatingip with a port which an
IPv4 and IPv6 address Neutron returns 'Bad floatingip request: Port %s
has multiple fixed IPs. Must provide a specific IP when assigning a
floating IP'.
While this is a helpful error message, it would be better if Neutron
could infer that the floating IP must be associated with the fixed-ip
of the same address family.
See also https://bugs.launchpad.net/neutron/+bug/1323766, restricting
floating IPs to IPv4 would simply things since associating an dual
stack floating IP with a dual stack port could result in any of the
following:
1. 1:1 NAT between the IPv4 address of the floating IP and IPv4 address of
the associated port.
2. 1:1 NAT between the IPv6 address of the floating IP and IPv6 address of the associated port.
3. Both 1 and 2 (Neutron presently only uses the first fixed-ip of the port owned by the floating IP)
4. a NAT-PT between the IPv4 address of the floating IP and IPv6 address of
the associated port
5. a NAT-PT between the IPv6 address of the floating IP and IPv4 address of
the associated port
Since NAT-PT and IPv6 NAT are not widely supported option 1 would be
preferable and the most intuitive of these results.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1469322/+subscriptions
References