Skip to content

Script returns error when service running task number is 0 #14

Description

@zheli

Right now the script returns error when a service has 0 running task number:

27-Jan-2017 15:53:57 ClientError: An error occurred (InvalidParameterException) when calling the DescribeTasks operation: Tasks cannot be empty.

In our case the running task number is changed by autoscale policy and sometimes it can be 0. Maybe we can catch this exception and just give a warning instead of error?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions