Retry logic needed when tagging subnets
rossf7 opened this issue · 1 comments
rossf7 commented
We had a failed cluster launch on Iris because a subnet could not be tagged with the cluster ID. The subnet was created so we should have retry logic for the tagging.
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:734","error":"could not create public subnet: [{/go/src/github.com/giantswarm/aws-operator/resources/aws/subnet.go:73: } {/go/src/github.com/giantswarm/aws-operator/resources/aws/subnet.go:98: } {InvalidSubnetID.NotFound: The subnet ID 'subnet-18485f70' does not exist\n\tstatus code: 400, request id: dc9c49bb-6e9f-4d71-b69d-7ac899959007}]","time":"17-08-02 16:13:07.015"}
xh3b4sd commented
FYI when using the operatorkit framework things like retries and metrics come for free.