Last modified: 2013-09-11 22:46:03 UTC
Fails with the following error message, on current master: Users/yuvipanda/code/vagrant/lib/mediawiki-vagrant/helpers.rb:18: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777 [default] Running provisioner: puppet... Running Puppet with site.pp... Could not run: Could not find node mediawiki-vagrant.dev The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! cd /tmp/vagrant-puppet/manifests && FACTER_virtualbox_version='4.2.16' FACTER_forwarded_port='8080' puppet apply --templatedir /vagrant/puppet/templates --node_terminus exec --external_nodes /vagrant/puppet/extra/puppet-classifier --verbose --config_version /vagrant/puppet/extra/config-version --logdest /vagrant/logs/puppet/puppet.ca0d886d.log --logdest console --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' site.pp --detailed-exitcodes || [ $? -eq 2 ]
This leaves vagrant in a state where nothing is served out, and hence unusable. Updated guest additions, no changes either.
Running destroy and up again fails with the same thing!
Ugh. This means a failure of the node classifier. If you can run 'vagrant ssh', please reply with the output of: /vagrant/puppet/extra/puppet-classifier If you can't 'vagrant ssh', just delete Roles.yaml and see if it fixes it.
vagrant@mediawiki-vagrant:~$ /vagrant/puppet/extra/puppet-classifier Roles.yaml does not contain a valid YAML manifest. Please fix the file, or delete it to have it regenerated. Error: Manifest document must be a mapping. My YAML file is empty. Is there docs for what to put in that somewhere?
rm'd Roles.yaml makes things works.
The underlying problem was that puppet-classifier was overly strict in its handling of Roles.yaml. First, there isn't much benefit in coercing the user to adopt a strict format when the data consists of class names, one per line. Second, because Puppet (stupidly) swallows both stdout and stderr of the child node classifier process, there was no way for puppet-classifier to actually emit an intelligible parse failure error. This meant that MediaWiki-Vagrant would break in a way that was very difficult to diagnose if you happened to have some non-YAML-compliant syntax in your Roles.yaml file. Fixed in I2f805dbde.
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]