yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #36243
[Bug 1437855] Re: Floating IPs should be associated with the first fixed IPv4 address
** Changed in: nova/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1437855
Title:
Floating IPs should be associated with the first fixed IPv4 address
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) kilo series:
Fix Released
Bug description:
If a port attached to an instance has multiple fixed IPs and a
floating IP is associated without specifying a fixed ip to associate,
the behavior in Neutron is to reject the associate request. The
behavior in Nova in the absence of a specified fixed ip, however, is
to pick the first one from the list of fixed ips on the port.
This is a problem if an IPv6 address is the first on the port because
the floating IP will be NAT'ed to the IPv6 fixed address, which is not
supported. Any attempts to reach the instance through its floating
address will fail. This causes failures in certain scenario tests that
use the Nova floating IP API when dual-stack IPv4+IPv6 is enabled,
such as test_baremetal_basic_ops in check-tempest-dsvm-ironic-pxe_ssh
in https://review.openstack.org/#/c/168063
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1437855/+subscriptions
References