You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> terraform apply
...
huaweicloud_rds_instance.instance: Still creating... [6m30s elapsed]
huaweicloud_rds_instance.instance: Still creating... [6m30s elapsed]
Error: error rebooting for RDS instance (**rds_id**): Expected HTTP response code [200 202] when accessing [POST https://rds.sa-brazil-1.myhuaweicloud.com/v3/**project_id**/instances/**rds_id**/action], but got 409 instead.
│ request_id: **request_id**, error message: {"error_msg":"Another operation is being performed on the DB instance or the DB instance is faulty.","error_code":"DBS.200452"}
│
│ with huaweicloud_rds_instance.instance,
│ on main.tf line 33, in resource "huaweicloud_rds_instance" "instance":
│ 33: resource "huaweicloud_rds_instance" "instance" {
> terraform plan
...
Terraform will perform the following actions:
# huaweicloud_rds_instance.instance is tainted, so must be replaced
-/+ resource "huaweicloud_rds_instance" "instance" {
...
Expected Behavior
RDS should be created successfully and saved to the state file.
Actual Behavior
RDS instance is created in the cloud account, the parameter is updated (confirmed in the Console), but since the parameter cron.timezone is only effective upon reboot, Terraform attempted to reboot the instance. The reboot failed (as seen in the error message above), so Terraform considers the RDS instance is tainted and replaces it in the next time terraform apply is executed.
Steps to Reproduce
terraform init
terraform apply -- it fails to reboot the instance
terraform apply -- it shows the RDS resource is tainted and needs to be replaced
Additional Context
cron.timezone parameter from RDS for PostgreSQL instance is only effective upon reboot.
The text was updated successfully, but these errors were encountered:
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/gutierrezps/fa02621e7fa549b3ab8b7d64f2507bbb
Expected Behavior
RDS should be created successfully and saved to the state file.
Actual Behavior
RDS instance is created in the cloud account, the parameter is updated (confirmed in the Console), but since the parameter
cron.timezone
is only effective upon reboot, Terraform attempted to reboot the instance. The reboot failed (as seen in the error message above), so Terraform considers the RDS instance is tainted and replaces it in the next timeterraform apply
is executed.Steps to Reproduce
terraform init
terraform apply
-- it fails to reboot the instanceterraform apply
-- it shows the RDS resource is tainted and needs to be replacedAdditional Context
cron.timezone
parameter from RDS for PostgreSQL instance is only effective upon reboot.The text was updated successfully, but these errors were encountered: