provider/openstack: Issues with Networking Ports and Fixed IPs

[jtopjian]

#12613 changed the way Fixed IPs were recorded in the Terraform state from TypeList (array) to a TypeSet (ordered list based on value hashing). This was to resolve the case when a user specified multiple fixed IPs in a non-alphanumeric order. The OpenStack Networking API returns Fixed IPs in alpha-numerical order, so the user would see a state change upon refresh.

Changing the attribute type from TypeList to TypeSet usually resolves this issue. However, doing this caused some issues for users expecting to find an IP address at element 0 of the fixed_ip attribute. It also causes state refreshes to happen when a user wants the fixed_ip to have an IP assigned via DHCP.

This issue is to collect the scenarios required to satisfy a working fixed_ip attribute and note the progress on resolution.

Scenarios:

• With TypeList, when a user specifies fixed_ips out of alphabetical/numerical order, they will see a state change upon refresh.
• With TypeSet, when a user specifies a single fixed_ip (which is probably the most commonly used scenario), they cannot easily reference the IP address of that IP, whether static or DHCP.
• With TypeSet, when a user specifies a fixed_ip with no ip_address, they will see a state change upon refresh.
• With TypeSet, there's no way, at the moment, to specify multiple fixed_ips with DHCP, since the hashing won't be able to accurately identify the fixed_ip upon first apply.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.