`vagrant up` fails with puppet on my machine

[benjajaja]

Hey I installed the exact vagrant and vb versions, and get this error after vagrant up:

==> default: Running provisioner: puppet...
==> default: Running Puppet with site.pp...
==> default: stdin: is not a tty
==> default: Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
==> default:    (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
==> default: Debug: Runtime environment: ruby_version=1.8.7, puppet_version=3.8.1, run_mode=user
==> default: Error: Could not parse for environment production: Syntax error at 'ensure' at /tmp/vagrant-puppet/manifests-32d629a2561383f270abbd7cb585fa75/site.pp:73:5 on node ubuntu-server-12042-x64-vbox4210
==> default: Error: Could not parse for environment production: Syntax error at 'ensure' at /tmp/vagrant-puppet/manifests-32d629a2561383f270abbd7cb585fa75/site.pp:73:5 on node ubuntu-server-12042-x64-vbox4210
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

My machine is ubuntu 14/trusty-something

[ProgrammerDan]

Probably just a screw up in the latest commit, lemme find a version that should be stable

[benjajaja]

ok, thanks!!!

[ProgrammerDan]

Use this commit: a9884a5

Just go headless -- git checkout a9884a5

That should work better :).

Be sure to clean up everything that failed; if puppet fails it means the VM was provisioned, so before trying vagrant up again, issue ./vagrant_cleanup.sh

[benjajaja]

yupp, that fixed it! thanks!

[ProgrammerDan]

Great. Now that folks are actually testing stuff, I'll need to be more careful about putting breaking changes in branches instead of main :D