You need to declare that

puppetdb::master::config

class on your compiler as well

Cool… so yeah, that’s probably the problem then. If your compiler isn’t configured to talk to PuppetDB, your agents that use that compiler won’t be in PuppetDB.

@vchepkov ++

vchepkov is on the rise! (Karma: 9)

This message was deleted.

This message was deleted.

Hello, I need some guidance in setting up a pki server. Basically we have a pki server which was manually installed and doesn't have the module and script in the puppet. I have to create a puppet module which can automatically install the pki servers in future and also save the scripts in puppet which can help us recover the server just incase if we loose the server...Thanks

for beaker we have https://github.com/voxpupuli/beaker and there is a lot of documentation when you goole 'puppet and beaker'

hi all, on Windows when I run

puppet agent -t

I get below error, does anyone know why? The key for agent is availabel on server:

PS C:\Users\> puppet agent -t

Warning: Unable to fetch my node definition, but the agent run will continue:

Warning: certificate verify failed [unable to get local issuer certificate for C

N=srv1]

Info: Retrieving pluginfacts

Error: /File[C:/ProgramData/PuppetLabs/puppet/cache/facts.d]: Failed to generate

additional resources using 'eval_generate': certificate verify failed [unable t

o get local issuer certificate for CN=srv1]

Error: /File[C:/ProgramData/PuppetLabs/puppet/cache/facts.d]: Could not evaluate

: Could not retrieve file metadata for puppet:///pluginfacts: certificate verify

failed [unable to get local issuer certificate for CN=srv1]

This message was deleted.

This message was deleted.

basically after puppet run catalog is not going to puppetdb

I deployed (along with puppetseerver and puppetdb) a puppetboard using the official puppetserver-helmchart. If I try to open / on that host, I get a 404 and according to the logs of the puppetboard container, it's from that container: 10.42.0.2 - - [22/Aug/20220947:05 +0000] "GET / HTTP/1.1" 404 232 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0" Do I have to use a prefix or something? Do I maybe need stuff in my puppetdb first?

I deployed (along with puppetseerver and puppetdb) a puppetboard using the official puppetserver-helmchart. If I try to open / on that host, I get a 404 and according to the logs of the puppetboard container, it's from that container: 10.42.0.2 - - [22/Aug/20220947:05 +0000] "GET / HTTP/1.1" 404 232 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0" Do I have to use a prefix or something?

I deployed (along with puppetseerver and puppetdb) a puppetboard using the official puppetserver-helmchart. If I try to open / on that host, I get a 404 and according to the logs of the puppetboard container, it's from that container: 10.42.0.2 - - [22/Aug/20220947:05 +0000] "GET / HTTP/1.1" 404 232 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0" Do I have to use a prefix or something? Do I maybe need stuff in my puppetdb first?

This message was deleted.

Another exported resource question - I'm trying to setup monitoring for a host with multiple services. In some cases the host name isn't something Puppet can a priori know (i.e. isn't based on

certname

or an IP address binding returned by

facter

) but might be shared by multiple applications. For instance, we might have a node Puppet knows as

<http://foo.example.com|foo.example.com>

that has a CNAME

<http://bar.example.com|bar.example.com>

our customers would know, with (say) both HTTP and PostgreSQL services we would like to monitor. My first thought is that we should export a host resource for

<http://bar.example.com|bar.example.com>

to our monitoring system, and then one service resource for each of the HTTP and PostgreSQL services, and have our monitoring system collect those resources. The problem is that both the HTTP and PostgreSQL classes need to export this host resource without causing a duplicate declaration. My understanding of exported resources is that I can't test the catalog of the exporting node since the resource would only exist in PuppetDB, and the catalog of the collecting node after collection. If this is wrong, please correct me. 🙂 I had a thought that I could query PuppetDB before export to see if that resource exists, for instance:

$r = puppetdb_query('resources{ type = "Profile::Monitoring::Host" and title = "<http://bar.example.com|bar.example.com>" and exported = true}')

And if the array

$r

is empty, then I know it's safe to export the resource. If it's not empty, then it's already been exported and doesn't have to be exported again. The problem is that I'm still getting a duplicate resource error, so this query or test doesn't seem to be working. Is this close to what I should be doing, or is there a better way to do it?

could be useful

could be useful

Interesting... Is the trick that it's wrapping the exported resource in a non-exported resource on the exporting node?

yeah, allows you to share, whatever 🙂

Brilliant, it works! Even had the wrapper type already, not sure why I thought it had to be exported too. Thanks!

stupid question but... can't seem to find a way to upgrade r10k on ubuntu, any advice? I originally installed it manually, but am now trying to manage it by puppetfile

beat me to it. It’s even in my clipboard