-
Bug
-
Resolution: Done
-
Undefined
-
None
-
Unspecified
-
False
-
-
False
-
-
-
Cloud Content Sprint 44
https://github.com/ansible-collections/amazon.aws/issues/2363
-
-
- Summary
-
When I try to create a new VPN with `amazon.aws.ec2_vpc_net` (collection v8.2.1) the *VPC is created in AWS* but the Ansible task fails (after some time) with this message:
> Failed to wait for IPv6 CIDR association
I can get no other details from Ansible
-
-
- Issue Type
-
Bug Report
-
-
- Component Name
-
ec2_vpc_net
-
-
- Ansible Version
-
Ansible is installed via Homebrew.
```console (paste below)
$ ansible --version
ansible [core 2.17.5]
config file = /Users/fabrizio.catalucci/workdir/ansible/ansible.cfg
configured module search path = ['/Users/fabrizio.catalucci/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /opt/homebrew/Cellar/ansible/10.5.0/libexec/lib/python3.12/site-packages/ansible
ansible collection location = /Users/fabrizio.catalucci/.ansible/collections:/usr/share/ansible/collections
executable location = /opt/homebrew/bin/ansible
python version = 3.12.7 (main, Oct 1 2024, 02:05:46) [Clang 15.0.0 (clang-1500.3.9.4)] (/opt/homebrew/Cellar/ansible/10.5.0/libexec/bin/python)
jinja version = 3.1.4
libyaml = True
```
-
-
- Collection Versions
-
```console (paste below)
$ ansible-galaxy collection list
Collection Version
---------------------------------------- -------
amazon.aws 8.2.1
ansible.posix 1.6.2
community.aws 8.0.0
community.general 9.5.0
prometheus.prometheus 0.19.0
```
-
-
- AWS SDK versions
-
```console (paste below)
$ pip3.12 show boto boto3 botocore
WARNING: Package(s) not found: boto
Name: boto3
Version: 1.34.109
Summary: The AWS SDK for Python
Home-page: https://github.com/boto/boto3
Author: Amazon Web Services
Author-email:
License: Apache License 2.0
Location: /Users/fabrizio.catalucci/Library/Python/3.12/lib/python/site-packages
Requires: botocore, jmespath, s3transfer
Required-by:
—
Name: botocore
Version: 1.34.109
Summary: Low-level, data-driven core of boto 3.
Home-page: https://github.com/boto/botocore
Author: Amazon Web Services
Author-email:
License: Apache License 2.0
Location: /Users/fabrizio.catalucci/Library/Python/3.12/lib/python/site-packages
Requires: jmespath, python-dateutil, urllib3
Required-by: boto3, s3transfer
```
-
-
- Configuration
-
```console (paste below)
$ ansible-config dump --only-changed
CACHE_PLUGIN(/Users/fab/workdir/ansible/ansible.cfg) = ansible.builtin.jsonfile
CACHE_PLUGIN_CONNECTION(/Users/fab/workdir/ansible/ansible.cfg) = /tmp/ansible_facts
CALLBACKS_ENABLED(/Users/fab/workdir/ansible/ansible.cfg) = ['community.general.log_plays']
CONFIG_FILE() = /Users/fab/workdir/ansible/ansible.cfg
DEFAULT_GATHERING(/Users/fab/workdir/ansible/ansible.cfg) = smart
DEFAULT_HOST_LIST(/Users/fab/workdir/ansible/ansible.cfg) = ['/Users/fab/workdir/ansible/inventory']
DEFAULT_LOAD_CALLBACK_PLUGINS(/Users/fab/workdir/ansible/ansible.cfg) = True
INTERPRETER_PYTHON(/Users/fab/workdir/ansible/ansible.cfg) = auto_silent
INVENTORY_CACHE_ENABLED(/Users/fab/workdir/ansible/ansible.cfg) = True
INVENTORY_CACHE_PLUGIN(/Users/fab/workdir/ansible/ansible.cfg) = ansible.builtin.jsonfile
INVENTORY_CACHE_PLUGIN_CONNECTION(/Users/fab/workdir/ansible/ansible.cfg) = /tmp/ansible_inventory
TRANSFORM_INVALID_GROUP_CHARS(/Users/fab/workdir/ansible/ansible.cfg) = always
```
-
-
- OS / Environment
-
MacBook Pro
Chip: Apple M1 Pro
macOS: Sonoma 14.6.1
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin23)
Homebrew 4.4.2
-
-
- Steps to Reproduce
-
Tested with this simple playbook.
<!--- Paste example playbooks or commands between quotes below -->
```yaml (paste below)
- name: Deploy AWS infrastructure
hosts: localhost
gather_facts: false
become: false
tasks: - name: VPC
amazon.aws.ec2_vpc_net:
name: "jira-dev2-vpc"
cidr_block: - "10.234.4.0/22"
dns_hostnames: false
dns_support: true
ipv6_cidr: false
tenancy: "default"
tags:
env: "dev2"
app: "jira"
state: present
register: vpc
```
-
-
- Expected Results
-
Since VPC is correctly created in AWS, I expected the task to succeed in Ansible as well.
-
-
- Actual Results
-
VPC is immediately created in AWS, but the Ansible playbook seems stuck for 5 minutes, then fails like this:
```console (paste below)
TASK [VPC] **************************************************************************************************
fatal: [localhost]: FAILED! =>
```
-
-
- Code of Conduct
-
- [X] I agree to follow the Ansible Code of Conduct