Fix: use correct primary NIC for External IP add/delete/refresh #6890
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
InstanceRunner
has been using the wrong primary NIC for Ephemeral/Floating IP addition/removal for some time, assuming that the Slot 0 NIC is always the primary. Now that External IP state is regularly re-asserted to keep Internet Gateway tags up-to-date, this led to OPTE ports reporting the use of external IPs on both the primary and slot0 nic, when multiple NICs are present and external IP state is changed on the instance.This PR makes the correct NIC selection for all three operations.