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
I am trying to setup consul as a backend w/ locking.
When I run env CONSUL_HTTP_SSL=true terraform apply -auto-approve=true -lock-timeout=100s -lock=true
and then right after in parallel I run env CONSUL_HTTP_SSL=true terraform apply -auto-approve=true -lock-timeout=100s -lock=true
With instance 2 I see...
Acquiring state lock. This may take a few moments...
data.vsphere_datacenter.datacenter: Refreshing state...
data.vsphere_network.network: Refreshing state...
data.vsphere_datastore.datastore: Refreshing state...
data.vsphere_resource_pool.resource-pool: Refreshing state...
data.vsphere_virtual_machine.template: Refreshing state...
vsphere_virtual_machine.vm: Refreshing state... (ID: 42271ab5-6807-872e-2aab-faf26182bfc2)
Failed to save state: consul CAS failed with transaction errors: [0xc42022c280]
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.
ghost
locked and limited conversation to collaborators
Apr 4, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to setup consul as a backend w/ locking.
When I run
env CONSUL_HTTP_SSL=true terraform apply -auto-approve=true -lock-timeout=100s -lock=true
and then right after in parallel I run
env CONSUL_HTTP_SSL=true terraform apply -auto-approve=true -lock-timeout=100s -lock=true
With instance 2 I see...
This also occurs with plans and refreshes.
If I try to run again.... I see
DEBUG logs
The text was updated successfully, but these errors were encountered: