Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ec2_instance - fix instance creation with IPv6 #40334

Merged
merged 1 commit into from May 24, 2018

Conversation

saydamir
Copy link
Contributor

SUMMARY

When creating an AWS EC2 instance via ec2_instance_module with an IPv6 address, the mutually exclusive parameters are passed - Ipv6Addresses and Ipv6AddressCount.
https://docs.aws.amazon.com/cli/latest/reference/ec2/assign-ipv6-addresses.html#options

Ipv6AddressCount was deleted.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

ec2_instance_module

ANSIBLE VERSION
ansible 2.5.2
  config file = /home/d/repos/ansible/ansible.cfg
  configured module search path = [u'/home/d/repos/ansible/library']
  ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.12 (default, Nov 20 2017, 18:23:56) [GCC 5.4.0 20160609]
ADDITIONAL INFORMATION
      - ec2_instance:
          instance_type: t2.small
          key_name: '{{ key_name }}'
          image_id: ami-43a15f3e
          vpc_subnet_id: "{{ vpc_subnetwork_id }}" 
          network:
            interfaces:
                - ipv6_addresses:
                    - '{{ ipv6_addr }}'
  error:
    code: InvalidParameterCombination
    message: IPv6 addresses and IPv6 address count may not be specified on the same request
  msg: 'Failed to create new EC2 instance: An error occurred (InvalidParameterCombination) when calling the RunInstances operation: IPv6 addresses and IPv6 address count may not be specified on the same request'
  response_metadata:
    http_headers:
      connection: close
      date: Thu, 17 May 2018 13:51:04 GMT
      server: AmazonEC2
      transfer-encoding: chunked
    http_status_code: 400
    request_id: 12345678-1111-1111-1111-123456789012
    retry_attempts: 0

@ansibot
Copy link
Contributor

ansibot commented May 17, 2018

cc @ryansb
click here for bot help

@ansibot ansibot added affects_2.5 This issue/PR affects Ansible v2.5 aws backport This PR does not target the devel branch. bug This issue/PR relates to a bug. cloud community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. new_contributor This PR is the first contribution by a new community member. support:community This issue/PR relates to code supported by the Ansible community. labels May 17, 2018
@mkrizek mkrizek removed the needs_triage Needs a first human triage before being processed. label May 18, 2018
@ryansb ryansb merged commit 3f2831c into ansible:stable-2.5 May 24, 2018
gundalow pushed a commit to gundalow/ansible that referenced this pull request May 24, 2018
@saydamir saydamir deleted the stable-2.5 branch May 24, 2018 14:16
gothicx pushed a commit to gothicx/ansible that referenced this pull request Jun 9, 2018
jacum pushed a commit to jacum/ansible that referenced this pull request Jun 26, 2018
@ansible ansible locked and limited conversation to collaborators May 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.5 This issue/PR affects Ansible v2.5 aws backport This PR does not target the devel branch. bug This issue/PR relates to a bug. cloud community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. new_contributor This PR is the first contribution by a new community member. support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants