On 07/02/2011 03:20 PM, Eric Sorenson wrote:
This is usually because somewhere you have a File resource whose name
is a variable, and the variable's undefined.
And a common reason for that to happen is that you've
mistyped the variable name. Your design could be just fine.
This is a good reaso
This is usually because somewhere you have a File resource whose name
is a variable, and the variable's undefined. So either:
package { "whatever" : ... require => File["$somevariable"] }
- or -
file { "$somevariable": .. .blah blah }
On Jul 1, 6:24 pm, Michael Halligan wrote:
> I'm running
On 06/26/2011 02:01 PM, ssk1287 wrote:
Consider the following scenario.
a folder FOLDER 1 which is owned by the root as it should be
accessible to all users of the system.
That's your mistake, right there. If you want a folder
accessible to all users then make it group writable for
some gr
On Fri, Jul 1, 2011 at 6:24 PM, Michael Halligan wrote:
> I'm running Puppet 2.7.1 on the master as well as the agent and just
> received a new error which doesn't actually reference a module or a file, so
> I'm somewhat stuck as to how to debug this. Any pointers?
> The error is err: Could not r
You need to sign the client certificate first,
Did you do all the steps as described under
http://projects.puppetlabs.com/projects/1/wiki/Certificates_And_Security(example
section) ?
Ronen
On Sat, Jul 2, 2011 at 1:39 AM, newguy wrote:
> Hi guys,
> I am very new to puppet and am trying to insta
