Skip to content

Help users debug issues when AWS could not provision instances #936

Open
@deliahu

Description

@deliahu

Description

Sometimes the auto scaling group fails to spin up instances, e.g. if the user is at their instance limit (spot or on demand), or if AWS is out of capacity (less common but has happened, especially for spot instances). It should be more obvious to the user that this has happened. Usually this information is contained in the Activity History for the auto scaling group

Update: This is now covered for issues that arise during cortex cluster up, but not covered after the cluster has spun up (e.g. if cortex deploy stalls because the spot instance could not be provisioned). This could be handled with another input signal into the API status.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions