Add retry logic when tagging Route Tables
rossf7 opened this issue · comments
Fixes error with cluster creation.
The VPC Route Tables are tagged with a name that includes the cluster ID. However route tables are eventually consistent so we need to retry the tagging if it has not been created yet.
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:226","error":"error processing cluster '86kmx':
'[{/go/src/github.com/giantswarm/aws-operator/service/create/service.go:685: could not create route table: '[{/go/src/github.com/giantswarm/aws-operator/resources/aws/route_table.go:72: } {/go/src/github.com/giantswarm/aws-operator/resources/aws/route_table.go:95: } {InvalidRouteTableID.NotFound: The routeTable ID 'rtb-054ef26e' does not exist\n\tstatus code: 400, request id: 94bab8f1-1250-4fdd-8153-49beb8ec49d3}]'} {execution failed}]'","time":"2017-11-21 14:48:26.250"}