An action 'up' was attempted on the machine 'default'

[Neil Watson]

Greetings,

I'm getting this message using Vagrant 1.8.1 with Virtualbox 5.

==> default: Running provisioner: serverspec...
An action 'up' was attempted on the machine 'default',
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.

I think is has to do with having two providers in my Vagrant file.

  config.vm.provision "ansible" do |ansible|
     ansible.verbose = 'v'
     ansible.playbook = "solr.yml"
  end

  config.vm.provision "serverspec" do |spec|
     spec.pattern = 'spec/default/*_spec.rb'
  end

What does the error mean and how can I fix it? 

[Alvaro Miranda Aguilera]

On Wed, Jul 20, 2016 at 6:15 AM, Neil Watson <neilh...@gmail.com> wrote:

config.vm.provision "serverspec"

Hello,

Not sure from where the error is comming from.

Could you test disabling one of those at the time ?

Then vagrant halt / vagrant up --provision 

maybe that will give some lights

Share back what you get from the issue you did open with the plugin owner.

https://github.com/jvoorhis/vagrant-serverspec/issues/27

Thanks

Alvaro,

[Neil Watson]

The trouble is that by default the plugin creates the line vagrant up #{host} in spec_helper.rb, assuming that the host is not already up.

[Alvaro Miranda Aguilera]

Maybe the use case from what the author of the plugin expect and your workflow are different?

Perhaps he does a check on first vagrant up to ensure the machine is fit?

If thats the case, I see the enhacement need to came from the plugin.

Ugly workaround would use check vagrant-triggers and do a shutdown after the first up?

seems ugly but may work in the meantime.

Other way would be move your provisioning script to packer, and create your own box, in that way you would be in the same workflow as the plugin serverspec.

Alvaro.

On Wed, Jul 20, 2016 at 8:13 AM, Neil Watson <neilh...@gmail.com> wrote:

The trouble is that by default the plugin creates the line vagrant up #{host} in spec_helper.rb, assuming that the host is not already up.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/dbd740f9-8783-4aa7-a901-5a4ee1505a2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.