Skip to content

Offline-Snapshot process does not wait until EC2 instance is in standby #47

@mbloch1986

Description

@mbloch1986

At the beginning of the oflfine-snapshot process EC2 instances of the Author-Dispatcher & Publish-Dispatcher are getting moved into standby. As configured in the Classic Load Balancer Draining Policy or in the ALB Target Group deregistration_delay configuration, it can take up to 5 minutes until those EC2 instances are in standby.

The offline-snapshot process will fail in the scenario where it takes up to 5 minutes to move the EC2 instances into standby and the offline-snapshot process finishes within 5 minutes. Because the process tries to move the ec2 instances from standby into in service at the end, while those ec2 instances are not in standby yet.

Lambda Error message

ClientError: An error occurred (ValidationError) when calling the ExitStandby operation: The instance i-... is not in Standby.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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