Changing the aws_autoscale_group min_size recreates the securitygroups, autoscaling group

[jedi4ever]

• I've started an autoscale setup with min_size zero.
• I then adjusted the min_size to 1 (only change) and it started recreating
• it seems during the first run, the template was not picked up as the count was 0?
• and it starts recreating security_groups , launch_configs

~ aws_autoscaling_group.elastic
    min_size: "0" => "1"

~ aws_autoscaling_group.webfarm
    min_size: "0" => "1"

-/+ aws_launch_configuration.elastic
    associate_public_ip_address: "false" => "0"
    ebs_block_device.#:          "0" => "<computed>"
    ebs_optimized:               "false" => "<computed>"
    image_id:                    "ami-c5b7d8b2" => "ami-c5b7d8b2"
    instance_type:               "t2.micro" => "t2.micro"
    key_name:                    "" => "<computed>"
    name:                        "elastic_config" => "elastic_config"
    root_block_device.#:         "0" => "<computed>"
    security_groups.#:           "1" => "1"
    security_groups.3398117304:  "sg-27bc9a42" => "sg-27bc9a42"
    user_data:                   "51edb70a69947c87e5423a8b3dadc2805527dec7" => "4049e07bd5a1c9657cf7d2f75d5e6e8fd5b4aa29" (forces new resource)

-/+ aws_launch_configuration.webfarm
    associate_public_ip_address: "false" => "0"
    ebs_block_device.#:          "0" => "<computed>"
    ebs_optimized:               "false" => "<computed>"
    image_id:                    "ami-c5b7d8b2" => "ami-c5b7d8b2"
    instance_type:               "t2.micro" => "t2.micro"
    key_name:                    "" => "<computed>"
    name:                        "web_config" => "web_config"
    root_block_device.#:         "0" => "<computed>"
    security_groups.#:           "1" => "1"
    security_groups.469441690:   "sg-26bc9a43" => "sg-26bc9a43"
    user_data:                   "4c14548b4972c39811f4bef6c68c19d12b3a1080" => "faa5ba12867c4e84f60c78a4014e7f56c7aab1ab" (forces new resource)**

-/+ aws_security_group_rule.allow_elastic_elb_to_elastic_instance
    from_port:                "9200" => "9200"
    protocol:                 "tcp" => "tcp"
    security_group_id:        "sg-27bc9a42" => "sg-27bc9a42"
    self:                     "false" => "0"
    source_security_group_id: "sg-27bc9a42" => "sg-25bc9a40" (forces new resource)
    to_port:                  "9200" => "9200"
    type:                     "ingress" => "ingress"

+ aws_security_group_rule.allow_elastic_to_elastic_instance
    from_port:                "" => "9200"
    protocol:                 "" => "tcp"
    security_group_id:        "" => "sg-27bc9a42"
    self:                     "" => "1"
    source_security_group_id: "" => "<computed>"
    to_port:                  "" => "9200"
    type:                     "" => "ingress"

+ template_file.elastic-userdata
    filename: "" => "user-data.elastic"
    rendered: "" => "<computed>"

+ template_file.web-userdata
    filename: "" => "user-data.web"
    rendered: "" => "<computed>"

[jedi4ever]

seems something else is going on:

• template checksum is changing everytime
• a self referencing aws group is being recreated.

will open another specific issue

[jedi4ever]

fwiw - I was hitting - #1962

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.