Floating IPs should be associated with the first fixed IPv4 address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Andrew Boik | ||
Kilo |
Fix Released
|
Undecided
|
Unassigned |
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_
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → Andrew Boik (drewboik) |
description: | updated |
description: | updated |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-1 → 12.0.0 |
tags: | removed: kilo-backport-potential |
Fix proposed to branch: master /review. openstack. org/168701
Review: https:/