Vvv: The comamnd "vagrant ssh -c 'vagrant_up'" fails while doing `vagrant up`

[sudar]

I did a git pull recently and with the current master I am getting the following error while running the vagrant up command.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: A newer version of the box 'ubuntu/trusty64' is available! You currently
==> default: have version '20160201.0.0'. The latest is version '20160217.1.0'. Run
==> default: `vagrant box update` to update.
==> default: VirtualBox VM is already running.
==> default: Checking for host entries
==> default: Running triggers after up...
==> default: Executing command "vagrant ssh -c vagrant_up"...
==> default: bash: vagrant_up: command not found
==> default: Command execution finished.
The command "vagrant ssh -c 'vagrant_up'" returned a failed exit code. The
error output is shown below:

bash: vagrant_up: command not found

I did some debugging and found that this line was introduced in #782

If I revert to master before this commit, then the vagrant up command works without any issues.

[mbootsman]

@sudar Having the same issue here.
How did you revert to the master before the commit?

[sudar]

@mbootsman I ran the following command in my vvv git repo directory

git checkout 53e2dcd

This is just a temporary fix till master is fixed. Once master if fixed, you may have to revert to master by using the following commands.

git checkout master
git pull origin master

[mbootsman]

@sudar Thanks, that did the trick :+1:

[cfoellmann]

Will Look into this this evening.
Did all of you install and/or reinstall the vagran triggers plugin?

[sudar]

@cfoellmann

No. I didn't re-install vagrant trigger plugin.

The only change I did is to do a git pull origin master in the directory where I have checked out vvv and then did a vagrant up.

I didn't even do a provision.

[mbootsman]

@cfoellmann No, only did a git pull origin master. I do have the vagrant triggers plugin installed.

[pdewouters]

same issue for me

[jeremyfelt]

As the vagrant_up script is new to the configuration, it's possible that it is not in its proper location inside the VM yet. Does this persist after doing a vagrant provision?

[pdewouters]

yes, running vagrat up --provision fixes the issue for me. thanks

[mbootsman]

Problem solved with vagrant up --provision, thanks!

[jeremyfelt]

Excellent! :+1:

For the next release we should note whether vagrant provision is required on upgrade.

[sudar]

I can also confirm that it works after doing a provision.

For the next release we should note whether vagrant provision is required on upgrade.

Yes, please. This would have saved me some time.

[Pezzab]

Hello, I get the same error but provisioning didn't fix the problem. Everything is up to date (including Virtual Box).

[GaryJones]

@Pezzab I had the same too, but I ran vagrant halt first, then vagrant up --provision and the error didn't appear.

[unknock]

Hi @cfoellmann
I get the same issue. I'm using Vagrant 1.8.1 on the Mac OS X. I tried both vagrant up and vagrant up --provision but it's not solved. This is my log.

==> default: Running triggers after up...
==> default: Executing command "vagrant ssh -c vagrant_up"...
==> default: bash: vagrant_up: command not found
==> default: Command execution finished.
The local command "vagrant ssh -c 'vagrant_up'" returned a failed exit
code or an exception. The error output is shown below:

bash: vagrant_up: command not found

Regards,

[PenneyGadget]

@techcoreJ try just vagrant provision - that worked for me while the other two didn't.

[cfoellmann]

Check/reinstall the vagrant triggers plugin

[kingluddite]

Yes. vagrant provision worked for me. The others did not.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.