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
Error: Provider produced inconsistent result after apply. azurerm_management_lock produced an unexpected new value: Root resource was present, but now absent.
#25674
Open
1 task done
ahosni-axon opened this issue
Apr 18, 2024
· 2 comments
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.db["photobook"].azurerm_management_lock.db[0], provider
│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" 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 Behaviour
The resource lock should have been created. The resource lock should have been added to the terraform state. The terraform apply should have completed successfully.
Actual Behaviour
The terraform apply created the DB successfully, but failed to create the lock. When the lock failed to create the terraform apply errored and stopped.
Steps to Reproduce
No response
Important Factoids
No response
References
#25667 Is a potentially related issue, as it provided the same error, however this issue is on a different version of terraform and the azurerm provider, as well as being caused by a different resource.
The text was updated successfully, but these errors were encountered:
Hi @ahosni-axon thanks for opening this issue. However, I could not reproduce this issue with the following TF config using the latest version of the Terraform provider. Could you please try using the following TF config in the latest version to see if the issue still exists?
Is there an existing issue for this?
Community Note
Terraform Version
AzureRM Provider Version
2.99.0
Affected Resource(s)/Data Source(s)
azurerm_management_lock
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The resource lock should have been created. The resource lock should have been added to the terraform state. The terraform apply should have completed successfully.
Actual Behaviour
The terraform apply created the DB successfully, but failed to create the lock. When the lock failed to create the terraform apply errored and stopped.
Steps to Reproduce
No response
Important Factoids
No response
References
#25667 Is a potentially related issue, as it provided the same error, however this issue is on a different version of terraform and the azurerm provider, as well as being caused by a different resource.
The text was updated successfully, but these errors were encountered: