Open coolapso opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
in the meantime implemented work around for this issue:
dynamic "auto_tune_options" {
for_each = var.os_autotune == "ENABLED" ? [1] : []
content {
desired_state = var.os_autotune
rollback_on_disable = "NO_ROLLBACK"
}
}
The above solution outlined by @4s3ti works until you attempt to downgrade an existing cluster and instance type which supports auto-tune and has it enabled. In which case, the same error will manifest when applying the terraform plan. The workaround there is to manually disable auto-tune in the AWS console before downgrading the instance type via tf.
I am stuck on this error too, the workaround did not work. so +1 Unable to use the Opensearch service.
I've hit the error while trying to reconfigure an existing T3 instance that had apparently had autotune enabled when it shouldn't have (but didn't have the agents) due to a bug in their deployment process.
AWS Support gave me the same answer as @tmielke-vizio suggests - manually disable autotune through the web UI before making changes. It isn't ideal, but it did work.
Terraform Core Version
0.13.7
AWS Provider Version
4.59.0
Affected Resource(s)
Expected Behavior
Resource created
Actual Behavior
Resource to be created
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Main Resource configuration:
Variables:
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
Resource plan output:
References
No response
Would you like to implement a fix?
None