I suppose in the latest puppet 3.x implementation if you specify --binder true, you don't necessary need to have hiera.yaml exists. Is that not a case?
-Chengkai On Thu, Nov 21, 2013 at 2:02 PM, Denmat <tu2bg...@gmail.com> wrote: > Two things, look at disabling detailed-exitcodes and use --hiera_conf to > declare the path to the hiera.yaml file. > > That should get you further. > Den > > On 22 Nov 2013, at 3:43, MM <wilddog.c.1...@gmail.com> wrote: > > So I had this confuse error message when running puppet via Vagrant puppet > provisioner with Puppet 3.3.2 and Data in Module > > > > > > > > > > > > > > > *Error: Could not run: Could not find file trueThe following SSH command > responded with a non-zero exit status.Vagrant assumes that this means the > command failed!puppet apply --binder true --ordering manifest --modulepath > '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' --manifestdir > /tmp/vagrant-puppet/manifests --detailed-exitcodes > /tmp/vagrant-puppet/manifests/default.pp || [ $? -eq 2 ]Stdout from the > command:Stderr from the command:Error: Could not run: Could not find file > true* > > Here my file layout, > > . > ├── Gemfile > ├── Gemfile.lock > ├── Rakefile > ├── Vagrantfile > ├── data > │ ├── environment > │ └── node > ├── hiera.yaml > ├── puppet > │ ├── Puppetfile > │ ├── manifests > │ └── modules > └── r10k.yaml > > Vagrant is configured to run puppet as following, > > config.vm.define 'mysql_server' do | mysql | > mysql.vm.hostname = 'mysql-server.local' > mysql.vm.provision :puppet do | puppet | > puppet.options = [ > '--binder true', > '--ordering manifest', > ] > puppet.manifests_path = 'puppet/manifests' > puppet.manifest_file = 'default.pp' > puppet.module_path = 'puppet/modules' > end > > So my question is what does error message mean? Do I need to tell puppet > where to look hiera.yaml anywhere in host or guest? > > Thanks, > -wd > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/5a33e4a4-b341-4250-bbfb-5fb7a98674b5%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/ShzTKgDl7_s/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/57836F99-7247-4EAA-86FE-E338B385DF1D%40gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANTbHr8MO0GFDaek1Pk5n9Hyqu_3KNh41pBHuDY3C_cwwQ%2BuGw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
