Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Untracked aws.autoscaling.Group pulumi resource if fail to create any healthy instance #5178

Open
jackwtech opened this issue Feb 7, 2025 · 0 comments
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team

Comments

@jackwtech
Copy link

Describe what happened

When use pulumi-aws to create an autoscaling group, if the autoscaling group fails to launch an instance successfully (not getting at least 1 healthy instance), pulumi will return a timeout error on creating the autoscaling group. A pulumi resource aws.autoscaling.Group is not created. See below:

  aws:autoscaling:Group (test-untracked-asg):
    error:   sdk-v2/provider2.go:520: sdk.helper_schema: waiting for Auto Scaling Group (untracked-asg-20250207025512285500000001) capacity satisfied: timeout while waiting for state to become 'ok' (last state: 'want at least 1 healthy instance(s) in Auto Scaling Group, have 0', timeout: 10m0s): [email protected]
    error: 1 error occurred:
    	* waiting for Auto Scaling Group (untracked-asg-20250207025512285500000001) capacity satisfied: timeout while waiting for state to become 'ok' (last state: 'want at least 1 healthy instance(s) in Auto Scaling Group, have 0', timeout: 10m0s)

However, the autoscaling group is physically created in AWS but just no healthy instance in the autoscaling. The autoscaling group is untracked by pulumi.

Sample program

launch_temp_name = ...
subnet_ids = [...]

aws.autoscaling.Group(
    "test-untracked-asg",
    name_prefix="untracked-asg-",
    max_size=1,
    min_size=1,
    desired_capacity=1,
    launch_template=aws.autoscaling.GroupLaunchTemplateArgs(
        name=launch_template_name,
        version="$Default",
    ),
    health_check_grace_period=300,
    health_check_type="ELB",
    vpc_zone_identifiers=subnet_ids,
    initial_lifecycle_hooks=[
        {
            "name": "abandon_hook",
            "default_result": "ABANDON",
            "heartbeat_timeout": 300,
            "lifecycle_transition": "autoscaling:EC2_INSTANCE_LAUNCHING",
        }
    ],
)

Log output

No response

Affected Resource(s)

aws.autoscaling.Group

Output of pulumi about

CLI
Version 3.138.0
Go Version go1.23.2
Go Compiler gc

Plugins
KIND NAME VERSION
resource aws 6.63.0
resource aws-native 1.7.0
resource azure 6.8.0
resource okta 4.11.3
language python unknown
resource random 4.16.7
resource time 0.1.0
resource tls 5.0.9

Host
OS debian
Version 12.9
Arch x86_64

This project is written in python: executable='/home/myproject/.venv/bin/python3' version='3.10.16'

// Stack info redacted

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@jackwtech jackwtech added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team
Projects
None yet
Development

No branches or pull requests

1 participant