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
The aws provider uses locking to allow parallel operation which results in this error
An action 'read_state' was attempted on the machine 'el7',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.
If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
The text was updated successfully, but these errors were encountered:
I've seen this in other situations, and I'm not sure it's caused by vagrant-hosts. For example, applying just the following provisioner to an AWS instance:
config.vm.provision:shell,inline=>'sleep 1000'
During the time that is running, vagrant ssh aws-vm from another terminal will fail with the "read_state" error above.
So, it seems like this is just bad locking behavior in Vagrant and not necessarily anything to do with vagrant-hosts.
The aws provider uses locking to allow parallel operation which results in this error
The text was updated successfully, but these errors were encountered: