We still need an underlying fix for two concurrent port updates that both try to set IPs. Our port update is a PUT action of the port body so we shouldn't throw errors to the user do to an internal race condition of IPAM.
For example, I shouldn't get an error if the port has IPs A and B and two concurrent port updates set the fixed_ips to just A.
We still need an underlying fix for two concurrent port updates that both try to set IPs. Our port update is a PUT action of the port body so we shouldn't throw errors to the user do to an internal race condition of IPAM.
For example, I shouldn't get an error if the port has IPs A and B and two concurrent port updates set the fixed_ips to just A.