You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to describe all of my VPCs in one AWS account where one of my VPC is a VPC shared from another account, I get the following error :
"msg": "Unable to describe if ClassicLink is enabled: An error occurred (InvalidVpcID.NotFound) when calling the DescribeVpcClassicLink operation: The vpc ID 'vpc-XXXXXXXX' does not exist"
I expected the module to get info from the VPC because i can still describe it with describe_vpcs
Actual Results
[WARNING]: No inventory was parsed, only implicit localhost is available[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'PLAY [Describe VPCs] *******************************************************************************************************************************************************************************************************************************************************************************************************TASK [Gathering Facts] *****************************************************************************************************************************************************************************************************************************************************************************************************ok: [localhost]TASK [ec2_vpc_net_info] ****************************************************************************************************************************************************************************************************************************************************************************************************An exception occurred during task execution. To see the full traceback, use -vvv. The error was: botocore.exceptions.ClientError: An error occurred (InvalidVpcID.NotFound) when calling the DescribeVpcClassicLink operation: The vpc ID 'vpc-XXXXXXXX' does not existfatal: [localhost]: FAILED! => {"changed": false, "error": {"code": "InvalidVpcID.NotFound", "message": "The vpc ID 'vpc-XXXXXXXX' does not exist"}, "msg": "Unable to describe if ClassicLink is enabled: An error occurred (InvalidVpcID.NotFound) when calling the DescribeVpcClassicLink operation: The vpc ID 'vpc-XXXXXXXX' does not exist", "response_metadata": {"http_headers": {"cache-control": "no-cache, no-store", "connection": "close", "content-type": "text/xml;charset=UTF-8", "date": "Wed, 09 Feb 2022 16:49:19 GMT", "server": "AmazonEC2", "strict-transport-security": "max-age=31536000; includeSubDomains", "transfer-encoding": "chunked", "vary": "accept-encoding", "x-amzn-requestid": "XXXXXXXX"}, "http_status_code": 400, "request_id": "XXXXXXXX", "retry_attempts": 0}}PLAY RECAP *****************************************************************************************************************************************************************************************************************************************************************************************************************localhost : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Handle absence of classic link support for shared VPCs
Signed-off-by: GomathiselviS [email protected]
SUMMARY
Fixes#663
One of the Classic Link Limitations is that
You cannot link an EC2-Classic instance to a VPC that's in a different Region or a different AWS account..
When calling the DescribeVpcClassicLink operation on a shared VPC, it errors out saying "The vpc ID 'vpc-xxxx' does not exist".
This PR handles this error.
ISSUE TYPE
Bugfix Pull Request
COMPONENT NAME
ADDITIONAL INFORMATION
Reviewed-by: Mark Chappell <None>
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Oct 24, 2023
Formally start the rds deprecation process
SUMMARY
The rds module is based upon the deprecated boto (not boto3/botocore) SDK and its functionality has been replaced by the rds_instance, rds_snapshot and rds_instance_info modules.
ISSUE TYPE
Feature Pull Request
COMPONENT NAME
rds
ADDITIONAL INFORMATION
See also ansible-collections#632
Reviewed-by: Felix Fontein <None>
Reviewed-by: Markus Bergholz <[email protected]>
Reviewed-by: Jill R <None>
Reviewed-by: None <None>
Summary
When I try to describe all of my VPCs in one AWS account where one of my VPC is a VPC shared from another account, I get the following error :
Issue Type
Bug Report
Component Name
ec2_vpc_net_info
Ansible Version
$ ansible --version
Collection Versions
$ ansible-galaxy collection list
AWS SDK versions
$ pip show boto boto3 botocore
Configuration
$ ansible-config dump --only-changed
OS / Environment
Ubuntu 18.04
Steps to Reproduce
Expected Results
I expected the module to get info from the VPC because i can still describe it with describe_vpcs
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: