cc78a7fbad
It's possible for a cloud to have multiple private networks with overlapping IP ranges. In that case, the check for missing floating ips can erroneously match a floating ip for a different server. Ports are actually unique, and are the foreign key between these things. Instead of starting with list_floating_ips, start with listing the ports for the server. In the case where OpenStack isn't broken, this will be the same number of API calls. In the case where it is, there will be one extra call per server, but ultimately the output will be more correct - and the fix for the extra load on the cloud is to fix the nova/neutron port mapping. Also, fixed the spelling of supplemental. Story: 2000845 Change-Id: Ie53a2a144ca2ed812d5441868917996f67b6f454
8 lines
343 B
YAML
8 lines
343 B
YAML
---
|
|
fixes:
|
|
- Fixed an issue where shade could report a floating IP being attached
|
|
to a server erroneously due to only matching on fixed ip. Changed the
|
|
lookup to match on port ids. This adds an API call in the case where
|
|
the workaround is needed because of a bug in the cloud, but in most
|
|
cases it should have no difference.
|