terraform-aws-modules / terraform-aws-autoscaling

Terraform module to create AWS Auto Scaling resources 🇺🇦
https://registry.terraform.io/modules/terraform-aws-modules/autoscaling/aws
Apache License 2.0
292 stars 556 forks source link

Provider produced inconsistent final plan #170

Closed AugustasV closed 2 years ago

AugustasV commented 2 years ago

Provider produced inconsistent final plan

Error: Provider produced inconsistent final plan. Changes have been applied, but those errors appeared.

Versions

Reproduction

Steps to reproduce the behavior:

no yes

Code Snippet to Reproduce

Changes applied without those errors because it shows that pipeline job failed, but it's not.

Expected behavior

Applied changes without that errors

Actual behavior

Output Error: Provider produced inconsistent final plan error Error: Provider produced inconsistent final plan


When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" changed the planned action from Update to
DeleteThenCreate.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .arn: was
known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.availability_zones: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.max_instance_lifetime: was cty.NumberIntVal(0), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.capacity_rebalance: was cty.False, but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.default_cooldown: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.service_linked_role_arn: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.suspended_processes: was cty.SetValEmpty(cty.String), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .id: was
known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.placement_group: was cty.StringVal(""), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.health_check_type: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.launch_configuration: was cty.StringVal(""), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.load_balancers: was cty.SetValEmpty(cty.String), but now null.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .name_prefix:
was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for .name: was
cty.StringVal("bpm-eu1int-45"), but now cty.StringVal("bpm-eu1int-46").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for
module.dis.aws_autoscaling_group.autoscaling_group_with_rolling_update[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/aws" produced an invalid new value for
.launch_template[0].name: was known, but now unknown.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

ERROR: Terraform apply failed with exit code 1``
antonbabenko commented 2 years ago

Hi!

This is a bug in the provider, which should be reported in the provider's own issue tracker. and please provide input Terraform code snippet which produces an error.

AugustasV commented 2 years ago

@antonbabenko thanks for tips, where exactly, here? https://github.com/hashicorp/terraform-provider-aws/issues/new?assignees=&labels=&template=Bug_Report.md

antonbabenko commented 2 years ago

Yes

github-actions[bot] commented 1 year ago

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.