Running terraform plan for our Genesys Cloud environment keeps flagging drift on genesyscloud_routing_queue resources, but the actual config hasn’t changed. The error suggests a state lock conflict, yet no other runs are active.
Error: Error acquiring the state lock
Lock Info:
ID: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
Path: state.tfstate
Operation: OperationTypeApply
Who: @manila-dev
Version: 1.5.0
Created: 2023-10-27 14:32:01.123456 +0000 UTC
Info:
Output was captured so it could be preserved in the event of error.
The lock ID matches a previous apply that failed due to a timeout. I’ve tried terraform force-unlock with that ID, but it says the lock isn’t held. The backend is S3 with DynamoDB for locking.
Is there a known issue with the Genesys Cloud provider and state locks? Or should I manually remove the lock from DynamoDB? The queue IDs are static, so the drift detection is likely failing due to a cached state mismatch rather than actual resource changes.