[Puppet Users] Re: /var/opt/lib/pe-puppet/reports/$hostname yaml files not recent

petdb/1.4/connect_puppet_master.html > > On Monday, September 16, 2013 9:10:05 AM UTC-7, root wrote: >> >> Still cannot figure out why I have such a variety of dates for the yaml >> files that exist in /var/opt/lib/pe-puppet/reports/`hostname` on each node. >> Each no

[Puppet Users] Re: /var/opt/lib/pe-puppet/reports/$hostname yaml files not recent

ged or wants to change on each node. Thanks. On Saturday, September 14, 2013 3:16:35 PM UTC-4, root wrote: > Cross-posted from Puppet Enterprise Users: > > Is Puppet Enterprise (3.0) supposed to create a yaml file in > /var/opt/lib/pe-puppet/reports/$hostname every time it runs? Beca

[Puppet Users] /var/opt/lib/pe-puppet/reports/$hostname yaml files not recent

Cross-posted from Puppet Enterprise Users: Is Puppet Enterprise (3.0) supposed to create a yaml file in /var/opt/lib/pe-puppet/reports/$hostname every time it runs? Because the files in this directory on all my nodes are not very consistent and they are not recent. If I do a puppet run on the

Re: [Puppet Users] Distributing files from varied sources to a common location on the clients

uppet, but that might > be a lot of work in your environment. > > - Chad > > On Fri, Sep 13, 2013 at 3:35 PM, root > > wrote: > > Very new to Puppet. Tried various ways to do this and I'm not > particularly > > happy with any of them. > > >

Re: [Puppet Users] Distributing files from varied sources to a common location on the clients

uppet, but that might > be a lot of work in your environment. > > - Chad > > On Fri, Sep 13, 2013 at 3:35 PM, root > > wrote: > > Very new to Puppet. Tried various ways to do this and I'm not > particularly > > happy with any of them. > > >

[Puppet Users] Distributing files from varied sources to a common location on the clients

ctories to the file resource, it only uses the first directory in the array: file { '/opt/local/scripts': ensure => "present", #owner => "root", #group => "root", #mode => 0755, recur

Re: [Puppet Users] Selector within a resource -- location & syntax

gs that are always mode 755 in one > OS and mode 700 in another, it may be somewhat more concise to declare a > variable and use that: > > $dirmode = $operatingsystem ? { > "Solaris" => 0755, > default => 0700, > } > > ... > &

[Puppet Users] Selector within a resource -- location & syntax

Can anyone tell me why this is legal: file { "/etc/cron.d": owner => "root", group => "root", mode => $operatingsystem ? { 'Solaris' => "0755", default => "0700",

Re: [Puppet Users] crapload of files to check permissions and ownership

Yes, I do intend to list all the files and their expected mode and ownership, I just want to figure out the nicest, most succinct way to do that. Wildcards and recursive listings will do me no good -- these files are scattered all over. Thanks. On Friday, August 2, 2013 3:33:57 PM UTC-4,

[Puppet Users] crapload of files to check permissions and ownership

File { ensure => "present", owner => "root", group => "root", mode => 644, } file { "/etc/cobbler/modules.conf": content => template("cobbler/modules.conf"); "/etc/cobbler/dhcp.template": content => t

Re: [Puppet Users] Re: [Module team] Much ado about modules

Ah, that workes nicely, thanks. On Monday, July 8, 2013 2:02:46 PM UTC-4, Nan Liu wrote: > On Mon, Jul 8, 2013 at 10:55 AM, root >wrote: > > http://forge.puppetlabs.com/modules > > > -- You received this message because you are subscribed to the Google Groups &qu

[Puppet Users] Re: [Module team] Much ado about modules

Hello. It would be nice if there was a way to browse all modules on Puppet Forge. I can browse all the modules released by Puppet Labs @ http://forge.puppetlabs.com/puppetlabs, (same for any author for whom I know the username) but as far as I know, there is no way to browse all modules. (Per

[Puppet Users] puppet module search using an HTTP proxy

Can anyone confirm that PE 3.0 supports this? I exported $http_proxy correctly, I beleive. $ puppet module search something Notice: Searching *https://forge.puppetlabs.com*... Error: Could not connect to *https://forge.puppetlabs.com*

[Puppet Users] Puppet Enterprise Console Admin Tools page is blank

I just installed Puppet Enterprise 2.7 on Red Hat EL 5.8. The install wants an email address to use as a user name. I gave it one, but never received any confirmation email. Was I supposed to? I was able to use that email address to log in to the console. The Admin Tools page is empty, and

Re: [Puppet Users] access exported resources in template

Well, 3 years old or not, this is still in the first page of google results haha. I'm running puppet version 2.7.9 and the result of that template is a blank comment line for every instance of the Firewall::Rule type. If I replace 'resource[:comment]' with 'resource.type' then I can confirm that

Re: [Puppet Users] access exported resources in template

The resource[:property] method doesn't seem to work. I'm pretty new with puppet and only just learned ruby, so I was hoping someone could perhaps just point me in the right direction. Here's what I've got so far: <% scope.compiler.catalog.vertices.each do |resource| -%> <% if resource.type == "F

[Puppet Users] Undo

So.. I am evaluating Puppet Enterprise 2.5. I was messing with Live Management and I cloned a user account to all my nodes instead of just one. This overwrote the account settings on all my Solaris and SUSE with the account data from a RHEL server. I'd like to know how I would undo this, ple