This was caused by duplicate "ruby /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.2/bin/vagrant up <box>" processes running every time "vagrant up" or "vagrant provision" was called. Was resolved by uninstalling Ruby 2.1.5, installing Ruby 2.2.0, and re-installing Vagrant and VirtualBox from scratch. Don't know what helped but I'm back to a single ruby process now.
On Friday, January 23, 2015 at 2:08:31 AM UTC+1, Evgeny Goldin wrote: > > Hi, > > I have a Vagrantfile > <https://github.com/evgeny-goldin/playbooks/blob/master/Vagrantfile> with > VirtualBox and AWS provided instances. Vagrant v1.7.2. > When Ansible provisioner is running for one of AWS instances (which may > take a while) - I can't perform any operation on any other instance, > VirtualBox or AWS. > > $ vagrant provision *nexus* > ==> nexus: Running provisioner: ansible... > An action 'read_state' was attempted on the machine *'nexus-aws'*, > 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. > > When this happened - I was running Ansible provisioning on "nexus-aws" > instance and tried to provision at the same time a "nexus" VirtualBox > instance. > > Now, I can probably understand why "status" fails: > > $ vagrant status > An action 'read_state' was attempted on the machine 'nexus-aws', > but another process is already executing an action on the machine. > > .. it attempts to read a status of all AWS instances. But what's the > reason for not being able to perform a provisioning of box A while B is > being provisioned? > > Warm regards, > Evgeny > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
