fix ec2 regression when assigning a private IP without a public IP #52579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…shouldn't also be added to top level parameters for run_instances changelog
|
@s-hertel, just so you are aware we have a dedicated Working Group for aws. |
ansibot
added
affects_2.8
s-hertel
removed
the
needs_triage
ansibot
added
the
stale_ci
|
Fixed the problem for me and was double-checked in #48109 (comment) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If the private_ip has been provided for the new network interface it shouldn't also be added to top level parameters for run_instances
changelog
SUMMARY
Fixes #48109. Introduced in #43954 (nice spotting @gamuniz) so this should be backported to 2.7.
ISSUE TYPE
COMPONENT NAME
lib/ansible/modules/cloud/amazon/ec2.py