-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Bug]: │ This is a bug in the provider, which should be reported in the provider's own issue tracker. #38461
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Same issue here with Terraform Core Version AWS Provider Version Error:
Resolved by pinning AWS provider to |
Relates #38016. |
@chrisolido @jared-rowe Thanks for reporting this issue 👏.
|
@ewbankkit We are seeing it on new deployments. during the apply it doesnt show a container task definition in the resource # module.container_ui[0].aws_ecs_task_definition.this will be created
+ resource "aws_ecs_task_definition" "this" {
+ arn = (known after apply)
+ arn_without_revision = (known after apply)
+ cpu = "256"
+ execution_role_arn = (known after apply)
+ family = "example"
+ id = (known after apply)
+ memory = "512"
+ network_mode = "awsvpc"
+ requires_compatibilities = [
+ "FARGATE",
]
+ revision = (known after apply)
+ skip_destroy = false
+ tags = {
+ "Name" = "example"
}
+ tags_all = {
+ "Environment" = "development"
+ "EnvironmentName" = "DW037"
+ "Name" = "example"
+ "Owner" = "example"
+ "Pipeline" = "https://example.com/devops-terraform-modules/example/-/pipelines/130717"
+ "Terraform" = "true"
}
+ task_role_arn = (known after apply)
+ track_latest = false
} If we replay this CI job, then it does go ahead and redeploy the resources successfully and the apply shows the container_defs on the second run # module.container_ui[0].aws_ecs_task_definition.this will be created
+ resource "aws_ecs_task_definition" "this" {
+ arn = (known after apply)
+ arn_without_revision = (known after apply)
+ container_definitions = jsonencode(
[
+ {
+ Command = null
+ Cpu = 0
+ CredentialSpecs = null
+ DependsOn = null
+ DisableNetworking = null
...
...
...
+ VolumesFrom = null
+ WorkingDirectory = null
},
]
)
+ cpu = "256"
... In our case the error was
|
Hi
Hi @ewbankkit - thanks for jumping on this quickly. Errors are occurring with new deployments creating new task definitions with
|
See #38482 which I closed as duplicate, this issue was introduced in version v5.59.0 downgrading to v5.58.0 works as expected. |
@aldenbe You made my week! Downgrading to v5.58.0 also worked for my new task deployments. I did a lot of debugging the last days to find out what is causing the issue but couldn't find anything. |
@jared-rowe Thanks for your example configuration -- we can reproduce the issue with it. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.60.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Terraform Core Version
0.9.1
AWS Provider Version
5.59.0
Affected Resource(s)
Circle CI
Expected Behavior
Should run the release smoothly
Actual Behavior
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
Exited with code exit status 1
Relevant Error/Panic Output Snippet
Terraform Configuration Files
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
Steps to Reproduce
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
Debug Output
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
Panic Output
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
Important Factoids
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
References
│
│ 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.crs.aws_ecs_task_definition.taskDefinition to include new values learned so far during apply
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: