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

aws_config_configuration_aggregator -> "Error: Provider produced inconsistent result after apply" #17139

Closed
tankcdr opened this issue Jan 15, 2021 · 3 comments
Labels
bug Addresses a defect in current functionality. service/configservice Issues and PRs that pertain to the configservice service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@tankcdr
Copy link

tankcdr commented Jan 15, 2021

Terraform CLI and Terraform AWS Provider Version

`
Terraform v0.14.2

  • provider registry.terraform.io/hashicorp/aws v3.24.1

`

Affected Resource(s)

aws_config_configuration_aggregator

Terraform Configuration Files

file: _config_org_aggregation.tf
`resource "aws_config_configuration_aggregator" "organization-config" {
count = var.config_org_aggregation_accounts == null ? 0 : 1
name = "${var.account_friendly_name}-org-config-aggregator"

account_aggregation_source {
account_ids = var.config_org_aggregation_accounts
all_regions = true
}
}`

file: modules.tf
`module "infosec_onboarding" {
source = "../../modules/onboarding"

baseline_tags = var.baseline_tags
account_friendly_name = var.onboarding_account_friendly_name
config_snapshot_delivery_frequency = var.onboarding_config_snapshot_delivery_frequency
config_storage_bucket_name = var.onboarding_config_storage_bucket_name
config_org_aggregation_accounts = var.onboarding_config_org_aggregation_accounts
}`

file: terraform.tfvars
###########################################
################# Onboarding Module parameters
###########################################
onboarding_account_friendly_name = "a name"
###########################################
################### AWS-Config parameters
onboarding_config_org_aggregation_accounts = ["account1", "account2", "account3", "account4"]
onboarding_config_storage_bucket_name = "com-someorganization-config-logs"
onboarding_config_snapshot_delivery_frequency = "TwentyFour_Hours"

Debug Output

`module.infosec_onboarding.aws_config_configuration_aggregator.organization-config[0]: Creating...

Error: Provider produced inconsistent result after apply

When applying changes to
module.infosec_onboarding.aws_config_configuration_aggregator.organization-config[0],
provider "registry.terraform.io/hashicorp/aws" produced an unexpected new
value: Root resource was present, but now absent.

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

Expected Behavior

The AWS Config aggregator would be created and terraform would not give an error.

Actual Behavior

The AWS Config aggregator is created, but terraform gives an error.

Steps to Reproduce

  1. terraform apply
@ghost ghost added the service/configservice Issues and PRs that pertain to the configservice service. label Jan 15, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 15, 2021
@bflad bflad added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 3, 2021
@bflad
Copy link
Contributor

bflad commented Mar 3, 2021

Related to #16796 for returning a better error message.

@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Feb 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/configservice Issues and PRs that pertain to the configservice service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

2 participants