[Puppet Users] Re: puppet certificate generate fails for mcollective client

I had this issue as well. To get around it you can pass an extra option: --certname This way it won't try to use your current host's FQDN as the certname (which will fail if it's already registered with the CA) So, e.g. puppet certificate generate treydock --certname treydock On Tuesday,

[Puppet Users] Re: Sending facts out-of-band natively

and instead use this custom command for maintenance/troubleshooting activities. On Thursday, September 11, 2014 10:11:10 AM UTC-4, Jon McKenzie wrote: > > Hi all, > > We're thinking about implementing the "puppet facts upload" pattern to > send facts up to the Puppetma

[Puppet Users] Sending facts out-of-band natively

Hi all, We're thinking about implementing the "puppet facts upload" pattern to send facts up to the Puppetmaster (and into Foreman) out-of-band. Basically, we need a way to distinguish hosts which are alive, but just have their agent disabled (e.g. for troubleshooting), and hosts which are jus

Re: [Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

08 PM, Paul Archer wrote: > > I see that puppet 3.3.2 has the problem as well. Worse, the > > documentation for 'puppet node' doesn't match the actual command. > > > > > > On Friday, December 13, 2013 11:13:26 AM UTC-6, Jon McKenzie wro

[Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

Re-upping this topic rather than creating a new one. I'm using Puppet 3.3.1 and am still having this problem. For example, if I run: puppet node find $(puppet config print certname) --render-as yaml The resulting YAML is missing ENC-set parameters (among other things). On the other hand, if I

[Puppet Users] Re: Class declaration ordering causes duplicate resource error

Thanks for the replies and being patient with me! Maybe I'm thinking about this incorrectly, but it seems to me that announcing a dependency ("I need x defined somewhere in order to work properly") shouldn't require a class to declare the dependency as well. It seems to me that the dependent cl

[Puppet Users] Re: Class declaration ordering causes duplicate resource error

uot;foo::bar"] } On Friday, November 15, 2013 5:27:11 PM UTC-5, jcbollinger wrote: > > > > On Friday, November 15, 2013 10:08:54 AM UTC-6, Jon McKenzie wrote: >> >> Has anyone run into this issue before? >> http://projects.puppetlabs.com/issues/5046#note-17 >>

[Puppet Users] Class declaration ordering causes duplicate resource error

Has anyone run into this issue before? http://projects.puppetlabs.com/issues/5046#note-17 Is there something obvious that I'm missing? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails fro

[Puppet Users] Node collecting its own exported resource

I'm writing a module in which nodes export a concat::fragment, collect all other nodes' analogous resource, and populate a config file (in this case, the krb5.conf for MIT Kerberos). It seems that nodes are not able to collect their own resource, but they can collect every other resource, with

Re: [Puppet Users] Question: Custom puppet type for semanage, converting inputs to flags?

Hi Dan, Thanks for the input. If I were to implement this in the provider, what would be the proper way to do that? Is there a validation/conversion hook I can override? On Sunday, September 9, 2012 1:55:17 PM UTC-4, Dan Bode wrote: > > > > On Sun, Sep 9, 2012 at 10:46 AM,

[Puppet Users] Re: Could not render to pson: undefined method 'merge' for []:Array

I restarted my puppetmaster and this seemed to resolve the issue. Very strange message, though. I suppose if I've defined a new type, but haven't restarted puppetmaster it throws a message like this? I will need to test that though On Sunday, September 9, 2012 4:16:53 PM UTC-4, Jo

[Puppet Users] Re: Could not render to pson: undefined method 'merge' for []:Array

I'm having this issue as well, with a nearly identical stack trace (I'm running on RHEL, however). Anyone have any ideas? I stuck some debugs inside my provider methods, but they don't ever seem to get executed. On Wednesday, July 11, 2012 4:08:42 PM UTC-4, Micah Martin wrote: > > This ones go

[Puppet Users] Question: Custom puppet type for semanage, converting inputs to flags?

Hi, I'm just trying to get an idea about the best way to implement this: I want a type that uses the 'semanage' binary to manage targeted policy (in this case for files). So for example to create a targeted policy, I might do something like: semanage fcontext -a -f -d -t some_domain_t "/path/t

[Puppet Users] Re: Manually creating class resource in site.pp works, calling same class from ENC silently fails

cript will silently skip the YAML config if it isn't readable (will now remedy that..). Thanks for your help -Jon On Friday, August 24, 2012 9:11:57 AM UTC-4, Jon McKenzie wrote: > > I altered my ENC script to get rid of the {} on empty params, and instead > follow what's prescribe

[Puppet Users] Re: Manually creating class resource in site.pp works, calling same class from ENC silently fails

nt, though, it still is only getting a subset of the defined ENC classes. I've tried stopping and restarting the web server as well, which doesn't appear to have any effect. I'm not sure what's going on On Thursday, August 23, 2012 8:37:24 PM UTC-4, Jon McKenzie wrote: > &

[Puppet Users] Re: Manually creating class resource in site.pp works, calling same class from ENC silently fails

! > > On Thursday, August 23, 2012 1:12:03 PM UTC-7, Jon McKenzie wrote: >> >> >> Is there a way on the server side to validate the ENC -> class >> transformation for clients? I can see in the logs when the ENC script gets >> run, but there's not m

[Puppet Users] Manually creating class resource in site.pp works, calling same class from ENC silently fails

I have a simple class, call it "foobar". It has two simple resources, a file and an augeas call to edit sysctl.conf. When I run my ENC script against a node, the class appears in the resulting YAML, e.g. --- classes: foobar: {} However, when I call 'puppetd --test' on the client side, this