twineapp / vagrant Goto Github PK

[Ubuntu 12.04]

Get the following CLI error when trying to run vagrant up:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && puppet apply --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' twine.pp --detailed-exitcodes || [ $? -eq 2 ]

The vagrant image will still run and access is still available to HTTP and SSH so I'm not sure what this error is in regards to.

Reported on Ubuntu 12.04

The following error is sticky whenever you try to use the vagrant commands against the vagrantfile:

There were warnings and/or errors while loading your Vagrantfile.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.

Warnings:
config.vm.customize calls are VirtualBox-specific. If you're
using any other provider, you'll have to find provider-specific configuration
to translate to manually in your Vagrantfile.```

Looks like the vagrant config isn't up to date with the latest version of Vagrant, it may be worth freezing at a specific Vagrant version as Vagrant provides a backlog of their versions.