Vagrant doesn't find puppet
Closed this issue · 5 comments
$ vagrant provision
==> default: Running provisioner: puppet...
The `puppet` binary appears not to be in the PATH of the guest. This
could be because the PATH is not properly setup or perhaps Puppet is not
installed on this guest. Puppet provisioning can not continue without
Puppet properly installed.
I think there is a misconfiguration of your box. I have to manually ssh to the box and yum install puppet.
I'm afraid I can't reproduce this issue with the base boxes. I double checked the latest boxes and both appear to have puppet 3.4.3 successfully installed in /usr/bin. I was also able to successfully run a basic puppet provisioner with freshly downloaded v20140311 boxes. See here for the minimal Vagrantfile and puppet example I used: https://gist.github.com/GUI/11321943 The same example worked on both the x86_64 and i386 boxes.
So a few questions:
- What version of the base boxes are you using?
- What version of Vagrant are you using?
- Are you doing anything else custom in your Vagrantfile? For example, are you using any Vagrant plugins, or are you using any other provisioners before puppet?
- I'm using CentOS-6.5-x86_64-v20140311.box, manually download the file from here and run
vagrant box add file:///CentOS-6.5-x86_64-v20140311.box centos-6.5 - I'm running Vagrant 1.5.1 with Virtualbox 4.3.10
- Just normal Vagrantfile with
vb.customize ["modifyvm", :id, "--memory", "1024"]and no other provisioner
Sorry for the delay in responding. I'm really not quite sure what could be causing this. I've released new versions of the boxes today, and I've re-verified that puppet is installed on them, so I'm going to close this. However, if you continue to encounter this problem with fresh vagrant provisions, can you let me know, and I'll re-open this?
Tested and it works. I've no issue with the new version. Thanks