Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatible with aws provider #48

Closed
jhoblitt opened this issue May 12, 2015 · 2 comments
Closed

Incompatible with aws provider #48

jhoblitt opened this issue May 12, 2015 · 2 comments

Comments

@jhoblitt
Copy link

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.
@Sharpie
Copy link
Member

Sharpie commented Feb 27, 2016

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.

@Sharpie
Copy link
Member

Sharpie commented Feb 27, 2016

Closing as a duplicate of mitchellh/vagrant-aws#428.

@Sharpie Sharpie closed this as completed Feb 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants