eddmann / serverless-fargate

Maintain long-running Fargate ECS tasks within your Serverless project
51 stars 21 forks source link

Error if schedule not set #20

Closed tw1t611 closed 2 years ago

tw1t611 commented 2 years ago

Deployment fails if schedule is not set for task

serverless.yml

org: timpolyma
app: birdzview
service: birdzview-fargate
frameworkVersion: "3"

provider:
  name: aws
  runtime: python3.9
  region: eu-central-1
  ecr:
    images:
      python:
        path: ./
        file: Dockerfile

  vpc:
    securityGroupIds:
      - birdzview-sg
    subnetIds:
      - birdzview

fargate:
  memory: "4GB"
  cpu: 2048
  logGroupName: fargate-log-group
  tasks:
    test:
      image: python
      # error if not set
      # schedule: "rate(1 day)"

plugins:
  - serverless-fargate

error:

Deploying birdzview-fargate to stage dev (eu-central-1, "default" provider)

✖ Stack birdzview-fargate-dev failed to deploy (30s)
Environment: linux, node 16.11.0, framework 3.21.0, plugin 6.2.2, SDK 4.3.2
Credentials: Serverless Dashboard, "default" provider (https://app.serverless.com/timpolyma/apps/birdzview/birdzview-fargate/dev/eu-central-1/providers)
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

Error:
CREATE_FAILED: TestService (AWS::ECS::Service)
Resource handler returned message: "Invalid request provided: CreateService error: Error retrieving subnet information for [birdzview]: The subnet ID 'birdzview' does not exist (ErrorCode: InvalidSubnetID.NotFound) (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 63c4ba55-a080-40e8-9ff3-4d5b43465d1c; Proxy: null)" (RequestToken: 236acdc6-f1e7-625c-e8dd-3aff8ae81613, HandlerErrorCode: InvalidRequest)

View the full error: https://eu-central-1.console.aws.amazon.com/cloudformation/home?region=eu-central-1#/stack/detail?stackId=arn%3Aaws%3Acloudformation%3Aeu-central-1%3A028655318971%3Astack%2Fbirdzview-fargate-dev%2F672a9e80-0c40-11ed-8e96-0646e2fbd7f4

Couldn't figure out, why SubnetID is a problem in that case.

eddmann commented 2 years ago

birdzview does not look to be a valid subnet id, these should be the subnet-* id that AWS has supplied.

eddmann commented 2 years ago

Did you manage to resolve this issue with a valid subnet id?

tw1t611 commented 2 years ago

Yes, I am using the default subnet-id now. It works. Closing. :)