giantswarm / aws-operator

Manages Kubernetes clusters running on AWS (before Cluster API)

Home Page:https://www.giantswarm.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error creating route table

puja108 opened this issue · comments

commented

On gaussI tried creating a cluster, which resulted in following error. The cluster showed up in our interfaces but no machines were created. The call was not retried.

A consecutive delete and recreation of the cluster did not show the same error, so it must have been temporary.

{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:472","info":"creating cluster 'er0xh'","time":"17-08-30 09:46:58.219"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:520","info":"created keypair 'er0xh'","time":"17-08-30 09:46:58.433"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:544","info":"created KMS key for cluster 'er0xh'","time":"17-08-30 09:47:03.691"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:609","info":"created bucket '084190472784-g8s-er0xh'","time":"17-08-30 09:47:06.001"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:626","info":"created vpc for cluster 'er0xh'","time":"17-08-30 09:47:06.633"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:649","info":"created gateway for cluster 'er0xh'","time":"17-08-30 09:47:06.867"}
{"caller":"github.com/giantswarm/aws-operator/service/create/security_group.go:56","info":"created security group 'er0xh-master'","time":"17-08-30 09:47:06.984"}
{"caller":"github.com/giantswarm/aws-operator/service/create/security_group.go:56","info":"created security group 'er0xh-worker'","time":"17-08-30 09:47:07.087"}
{"caller":"github.com/giantswarm/aws-operator/service/create/security_group.go:56","info":"created security group 'er0xh-ingress'","time":"17-08-30 09:47:07.179"}
{"caller":"github.com/giantswarm/aws-operator/service/create/service.go:481","error":"error processing cluster 'er0xh': '[{/go/src/github.com/giantswarm/aws-operator/service/create/service.go:727: could not create route table: '[{/go/src/github.com/giantswarm/aws-operator/resources/aws/route_table.go:66: } {/go/src/github.com/giantswarm/aws-operator/resources/aws/route_table.go:89: } {InvalidRouteTableID.NotFound: The routeTable ID 'rtb-1cac4177' does not exist\n\tstatus code: 400, request id: d381fed4-dbb3-420d-88e5-299e5acd932a}]'} {execution failed}]'","time":"17-08-30 09:47:10.583"}```

@rossf7 @fgimenez do you know more about this? Is this issue still relevant?

I don't think so, there have been some issues with leftover route tables that match the description, the aws-cleanup project and the upcoming cloudformation changes to aws-operator should make this much less likely to happen.

commented

closing