vagrant shared folder unable to provision Puppet

[nabobnagari]

Unbale to provision , Puppet executable files failed to to find apt folder

`VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "hashicorp/precise32"

config.vm.define :web do |web_config| web_config.vm.network :private_network, :ip => "192.168.33.12" web_config.vm.synced_folder ".", "/tmp/vagrant-puppet" web_config.vm.provision "puppet" do |puppet| puppet.module_path = "modules" puppet.manifest_file = "web.pp" end end

end`

web.pp

` class { ‘apt’: always_apt_update => true, }

Class[‘apt’] -> Package <| |>

Exec { path => ‘/usr/bin:/usr/sbin/:/bin:/sbin:/usr/local/bin:/usr/local/sbin’, }

package { [“tomcat7”]: ensure => installed, }

service { “tomcat7”: ensure => running, enable => true, hasstatus => true, hasrestart => true, require => Package[“tomcat7”], } `

web: Vagrant insecure key detected. Vagrant will automatically replace web: this with a newly generated keypair for better security. web: web: Inserting generated public key within guest... web: Removing insecure key from the guest if it's present... web: Key inserted! Disconnecting and reconnecting using new SSH key... ==> web: Machine booted and ready! ==> web: Checking for guest additions in VM... web: The guest additions on this VM do not match the installed version of web: VirtualBox! In most cases this is fine, but in rare cases it can web: prevent things such as shared folders from working properly. If you see web: shared folder errors, please make sure the guest additions within the web: virtual machine match the version of VirtualBox you have installed on web: your host and reload your VM. web: web: Guest Additions Version: 4.2.0 web: VirtualBox Version: 5.0 ==> web: [vagrant-hostsupdater] Checking for host entries ==> web: Configuring and enabling network interfaces... ==> web: Mounting shared folders... web: /tmp/vagrant-puppet => C:/junk/vagrant_test/test1 web: /tmp/vagrant-puppet/modules-ac9b601e8e3a3a3c572f23b9b26465ae => C:/junk/vagrant_test/test1/modules web: /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513 => C:/junk/vagrant_test/test1/manifests ==> web: Running provisioner: puppet... ==> web: Running Puppet with web.pp... ==> web: stdin: is not a tty ==> web: warning: Could not retrieve fact fqdn ==> web: Could not parse for environment production: Could not match `apt': at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/web.pp:1 on node precise32 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.

[nabobnagari]

Attached debug Log

log.txt

[QuinnyPig]

You're combining a modules path and a manifests path. Don't do that.

[nabobnagari]

puppet.module_path = "modules" puppet.manifest_file = "web.pp"

May I know which code line went wrong, Puppet unable to find apt folder .....?