53b1fc4cde
Currently the auto_ip logic checks for a public v4 address to determine if it should make a FIP. However, we have richer logic that provides interface_ip that takes in to account IPv6 as well as configured choices as to what the "default" network should be. That is what should really be cared about - does the server have an ip that would be considered the thing to connect to it on. Change-Id: Ica1feb31cc3477c6336a749c88f4706efd20484f
14 lines
686 B
YAML
14 lines
686 B
YAML
---
|
|
fixes:
|
|
- shade now correctly does not try to attach a floating ip with auto_ip
|
|
if the cloud has given a public IPv6 address and the calling context
|
|
supports IPv6 routing. shade has always used this logic to determine
|
|
the server 'interface_ip', but the auto floating ip was incorrectly only
|
|
looking at the 'public_v4' value to determine whether the server needed
|
|
additional networking.
|
|
upgrade:
|
|
- If your cloud presents a default split IPv4/IPv6 stack with a public
|
|
v6 and a private v4 address and you have the expectation that auto_ip
|
|
should procure a v4 floating ip, you need to set 'force_ipv4' to True in
|
|
your clouds.yaml entry for the cloud.
|