On Fri, Apr 12, 2013 at 12:23:45PM -0700, Larry Fast wrote: > Windows NuBQ: > I'm running windows with a clean install of puppet and an empty node > definition. puppet agent -t pauses with no prompt. When I hit enter, I > get this warning: > > Using Facter::Util::Resolution.exec with a shell built-in is deprecated. > Most built-ins can be replaced with native ruby commands. If you really > have to run a built-in, pass "cmd /c your_builtin" as a command > > How do I fix/disable this warning?
I'm facing a similar problem, on one single Windows machine out of more than 100. If I run any puppet command, I get above warning. Additionally, it can't execute the following simple class to update the puppet.conf file: class puppetconf { service { 'PuppetAgent': name => 'puppet', ensure => 'running', enable => 'true', subscribe => File['puppet.conf'], } file { 'puppet.conf': path => 'C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf', ensure => file, source => 'puppet:///modules/puppetconf/puppet.conf', } } It fails with the following error: Error: /Service[PuppetAgent]: Could not evaluate: Could not find init script for 'puppet' It looks like it somehow thinks it isn't running on a Windows machine. I've read this thread but the solution given here doesn't apply to my setup. There are no custom facts added, and the few modules installed from PuppetForge work fine on all the other machines. Anything else I could do to resolve this issue? Thanks... Dirk -- Dirk Heinrichs <dirk.heinri...@altum.de> Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913 GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de
signature.asc
Description: Digital signature