Yes, the actual subnet id was subnet-0f18a0d4a7e9c7719. I was concerned
that putting the subnet ID and other IDs into here might (somehow?) be a
security issue. I've deleted the whole VPC now, so it won't be a problem.
Here's the additional debug (which all looks fine to my eyes!!)
TASK [aws_vpc : Routes | Debug public_subnets_to_az]
***************************************************************************************************************************************
task path:
/cup/core-kubernetes-linux/ansible/roles/aws_vpc/tasks/routes.yml:59
ok: [localhost] => {
"public_subnets_to_az": {
"subnet-0d6f53bad96008956": "eu-west-1c"
}
}
TASK [aws_vpc : Routes | Debug existing_nat_gateways.result]
*******************************************************************************************************************************
task path:
/cup/core-kubernetes-linux/ansible/roles/aws_vpc/tasks/routes.yml:74
ok: [localhost] => {
"existing_nat_gateways.result": [
{
"create_time": "2019-01-21T15:08:50+00:00",
"nat_gateway_addresses": [
{
"allocation_id": "eipalloc-0b86cd580c67ad534",
"network_interface_id": "eni-0907d51d9f17e3ff4",
"private_ip": "172.17.3.106",
"public_ip": "34.246.20.83"
}
],
"nat_gateway_id": "nat-01e48244fa76ff742",
"state": "available",
"subnet_id": "subnet-0d6f53bad96008956",
"tags": {},
"vpc_id": "vpc-07fd6abc9b3c96674"
},
{
"create_time": "2019-01-21T15:08:47+00:00",
"nat_gateway_addresses": [
{
"allocation_id": "eipalloc-0dd6969c7deb9b616",
"network_interface_id": "eni-00a24e6de1b45cdee",
"private_ip": "172.17.1.252",
"public_ip": "63.34.105.22"
}
],
"nat_gateway_id": "nat-0fd2bad6baffad428",
"state": "available",
"subnet_id": "subnet-0f18a0d4a7e9c7719",
"tags": {},
"vpc_id": "vpc-07fd6abc9b3c96674"
},
{
"create_time": "2019-01-21T15:08:49+00:00",
"nat_gateway_addresses": [
{
"allocation_id": "eipalloc-018a80fb6bd4a2efc",
"network_interface_id": "eni-0e8507f1ba250dfb9",
"private_ip": "172.17.2.18",
"public_ip": "63.34.176.76"
}
],
"nat_gateway_id": "nat-0fb938e1aa8784738",
"state": "available",
"subnet_id": "subnet-079e51dbe6bcaf502",
"tags": {},
"vpc_id": "vpc-07fd6abc9b3c96674"
}
]
}
On Tuesday, 22 January 2019 12:05:57 UTC, Karl Auer wrote:
>
> Use debug statements so that you know what is in "
> existing_nat_gateways.result" and "public_subnets_to_az".
>
> It looks to me as if there is no element called "subnet-0facefaceface9"
> in the dictionary "public_subnets_to_az" (that is a very cool subnet ID
> by the way).
>
> Regards, K.
>
> On Tue, Jan 22, 2019 at 10:51 PM Steve Button <[email protected]
> <javascript:>> wrote:
>
>> And the error message is :-
>>
>> The error appears to have been in
>> '/cup/core-kubernetes-linux/ansible/roles/aws_vpc/tasks/routes.yml': line
>> 62, column 3, but may\n
>>
>>
>> --
> Karl Auer
>
> Email : [email protected] <javascript:>
> Website: http://2pisoftware.com
>
> GPG/PGP : 958A 2647 6C44 D376 3D63 86A5 FFB2 20BC 0257 5816
> Previous: F0AB 6C70 A49D 1927 6E05 81E7 AD95 268F 2AB6 40EA
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/184cfbf5-f4b2-45c0-b26d-dbd9aec01e00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
