provider/aws: Retry ECS svc update on ServiceNotFoundException

[radeksimko]

This is to address the following test failures:

=== RUN   TestAccAWSEcsServiceWithFamilyAndRevision
--- FAIL: TestAccAWSEcsServiceWithFamilyAndRevision (11.63s)
    testing.go:280: Step 0 error: Error applying: 1 error(s) occurred:
        
        * aws_ecs_service.jenkins: 1 error(s) occurred:
        
        * aws_ecs_service.jenkins: ServiceNotFoundException: Service not found.
            status code: 400, request id: 7111c49f-49b4-11e7-8a31-1f4c10a1cce8
=== RUN   TestAccAWSEcsService_withAlb
--- FAIL: TestAccAWSEcsService_withAlb (187.15s)
    testing.go:280: Step 0 error: Error applying: 1 error(s) occurred:
        
        * aws_ecs_service.with_alb: 1 error(s) occurred:
        
        * aws_ecs_service.with_alb: ServiceNotFoundException: Service not found.
            status code: 400, request id: e22e863d-49b4-11e7-9e01-79f4e5b714b9

Here's a relevant snippet from the debug log:

2017/06/05 06:04:49 [DEBUG] [aws-sdk-go] DEBUG: Response ecs/UpdateService Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 400 Bad Request
Connection: close
Content-Length: 68
Content-Type: application/x-amz-json-1.1
Date: Mon, 05 Jun 2017 06:04:49 GMT
Server: Server
X-Amzn-Requestid: e22e863d-49b4-11e7-9e01-79f4e5b714b9


{"__type":"ServiceNotFoundException","message":"Service not found."}
-----------------------------------------------------

[stack72]

More eventual consistency issues?

Regardless, LGTM

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.