search

example42 / puppet-modules-nextgen

Example42 Puppet Modules Version 2.x
http://www.example42.com
Other
83 stars 23 forks source link

Puppi, Windows and Puppet 301 = problem #11

Closed larryfast closed 11 years ago

larryfast commented 11 years ago

Is this diagnosis correct: Even if I do not include any example42 modules in my node manifest, if puppi is on my modulepath and pluginsync=true all of puppi's *.rb files will be installed onto that node.

If the diagnosis is correct, this is my problem on my Windows nodes. I'm running Puppet 301. When nextgen_puppi is in my modulepath I get the following error:

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.

This halts the puppet run and waits for the operator to hit Enter. Worse still, the run halts before the message is displayed.

Any suggestions? My current plan is to make a special Windows environment that does not include the example42 modules.

Thanks Larry Fast

alvagante commented 11 years ago

Can you issue "facter -p" from a Windows shell and me where and if it blocks?

alvagante commented 11 years ago

This could fix the problem: https://github.com/example42/puppi/commit/0e146e4af1ba397f6934c1901cec30017f0841f2

larryfast commented 11 years ago

That fixed the problem, thanks! BTW, there is one other instance that I needed to wrap: puppi/lib/facter/last_run.rb Cheers, Larry Fast

alvagante commented 11 years ago

Good. last_run.rb was already confined (on github master, if you got puppi from the forge you've an outdated version)