[Puppet Users] Bolt 1.31.1 now available

[puppet-product-updates]

Greetings,

Bolt 1.31.1 is a bug fix release that addresses spurious plan failures and
warnings on startup.

For more information, check out the release notes:
https://puppet.com/docs/bolt/latest/bolt_resolved_issues.html#spurious-plan-failures-and-warnings-on-startup-1-31-1

To try this version of Bolt, follow the installation instructions for your
operating system:
https://puppet.com/docs/bolt/latest/bolt_installing.html

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAKi9oYbGMMXkenYY7SB9Xugx5iTMCRyBuFpwRo0YfZFnQHcEEA%40mail.gmail.com.

[Puppet Users] Bolt Developer Update (2019/09/27) — The Road to Bolt 2.0

[Nick Lewis]

The past few weeks have had some large features in flight and we're finally
seeing them land, so it's time for another update.

We released Bolt 1.31 and the big news is that our so-called plugin system
is now *actually* pluggable!

You can now bundle and ship inventory plugins as ordinary Bolt tasks in
modules. Currently that includes looking up targets and config (
resolve_reference), and secret encryption/decryption.

To write a module with a plugin, you need to do two things:
1) Add a bolt_plugin.json at the root of the module to tell Bolt that it
has plugins. For now, this can just contain {}.
2) Write a task with the same name as the plugin "hook" you want to
implement (this can be overridden in bolt_plugin.json later) that returns
an object with a value key.

For example, to turn the mymodule module into a plugin that can retrieve
targets, just add bolt_plugin.json and write a task called
mymodule::resolve_reference.

mymodule can then be referenced from the inventory. When Bolt runs, it will
run the task with whatever parameters you set and will substitute the
result in the inventory.

groups:
  - name: mynodes
targets:
  - _plugin: mymodule
user: nick
application: web

For a real world example, check out the puppetlabs-azure_inventory module
.

*Bolt 2, Inventory 2*

We also wanted to take some time to share some of our plans for the
upcoming Bolt 2.0 release.

The marquee feature of Bolt 2.0 is already coming into existence in Bolt
1.x. That's the new v2 inventory format and Target API.

The biggest change in the v2 inventory is how targets are defined and
managed. In inventory v1, a target always had a "name" field which was
parsed as a URI to determine connection information. That mixing of
identity with data caused trouble if you wanted to later change the
connection information for the target in a plan. For instance, if you
wanted to use a different transport.

In v2, a target separately has a "name" as well as connection information.
You can set both a URI as well as individual connection fields like host
and port. This makes it easier to dynamically modify and create new Targets
within a plan, which is helpful for plans that provision new nodes.

A related improvement is that arguments to parameters of type TargetSpec will
automatically be added to the inventory before the plan is run. For
example, the following plan:

plan test(TargetSpec $nodes) {
  return get_targets('all')
}

If you were to run this plan with an empty inventory.yaml file, for
instance with bolt plan run test --nodes foo,bar,baz, it would have
returned nothing, because the inventory was empty. With the v2 inventory,
it will return ["foo", "bar", "baz"], because those targets are added to
the inventory automatically.

Inventory v2 is also the only version which supports the plugin
functionality mentioned above. Inventory v2 is available for you to try out
in Bolt today and will be the only format in Bolt 2.0. Check out the docs
 to see how to
migrate your inventory.

We'll be back with more updates as Bolt 2.0 draws nearer. In the meantime,
you can follow the Bolt 2.0 milestone
 to see what's happening.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANa5_qJWEk5HV76M1NfGj82mnufLwQbdijy%3Db4PoS%2BY4fPMTBg%40mail.gmail.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Andreas Ntaflos]

On 27.09.19 18:11, Dan Crisp wrote:
> Thanks for the reply John,
> 
> The issue still persists unfortunately.
> 
> I've ensured that Selinux isn't enforcing on both the server side and
> client and then restarted the Puppet service on the master server.  The
> server logs whilst running the agent read as follows:

Are you positive the user and group really haven't been created?

And have you changed

node 'default' { ... }

to

node default { ... }

i.e. without the single quotes, as suggested? And afterwards restarted
the Puppetserver process by means of, e.g. systemctl restart puppetserver?

If so, and this hasn't helped, you may want to try to narrow the problem
down by simplifying the default node manifest even more, by making
site.pp look like this (verbatim):

node default {
  fail('Failing deliberately on default node manifest')
}

Don't forget to restart the Puppetserver after that to make sure the
change is picked up.

When you then run the Puppet agent on the troublesome node it should
fail hard with the message defined above. If it does then you know at
least that site.pp is read and a catalog is created and applied for that
node. If it does not then there must be something else amiss that is not
obvious from the information and details you posted.

HTH

Andreas

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/48f7aa63-ed60-d5c8-d36c-d302c01d4130%40ptmx.org.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Prevent duplicate resources

[Timo Vlot]

Hi All,

We recently start with Puppet and during our introductory consultancy it 
was mentioned that there is a "sneaky" way to define a resource (for 
example a pakcage) in multiple classes that wouldn't cause the "duplicate 
resource" errors. We have a few classes that rely on the same package being 
installed, but cannot guarantee they are all attached to a node, as such we 
would need to define the same package resource in all classes.

Does anyone know how to add a resource in multiple classes without the 
error?

thanx!

Timo

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b690bc99-46cc-4130-b7ea-8f03442aa16d%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thanks for the reply John,

The issue still persists unfortunately.

I've ensured that Selinux isn't enforcing on both the server side and 
client and then restarted the Puppet service on the master server.  The 
server logs whilst running the agent read as follows:

10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/node/lhcadvdeveye05.fixnetix.com?environment=production&transaction_uuid=4d2c88b1-2aec-45a5-bc7e-407c2ad8229e&fail_on_404=true
 
HTTP/1.1" 200 13535 10.20.25.83 10.20.25.83 8140 109
10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/file_metadatas/pluginfacts?environment=production&links=follow&recurse=true&source_permissions=use&ignore=.svn&ignore=CVS&ignore=.git&ignore=.hg&checksum_type=md5
 
HTTP/1.1" 200 220 10.20.25.83 10.20.25.83 8140 25
10.20.25.83 - - - 27/Sep/2019:16:06:43 + "GET 
/puppet/v3/file_metadatas/plugins?environment=production&links=follow&recurse=true&source_permissions=ignore&ignore=.svn&ignore=CVS&ignore=.git&ignore=.hg&checksum_type=md5
 
HTTP/1.1" 200 224 10.20.25.83 10.20.25.83 8140 16
10.20.25.83 - - - 27/Sep/2019:16:06:44 + "GET 
/puppet/v3/file_metadatas/locales?environment=production&links=follow&recurse=true&source_permissions=ignore&ignore=.svn&ignore=CVS&ignore=.git&ignore=.hg&ignore=%2A.pot&ignore=config.yaml&checksum_type=md5
 
HTTP/1.1" 200 224 10.20.25.83 10.20.25.83 8140 20
2019-09-27 16:06:44,620 INFO  [puppetserver] Puppet Compiled catalog for 
lhcadvdeveye05.fixnetix.com in environment production in 0.10 seconds
10.20.25.83 - - - 27/Sep/2019:16:06:44 + "POST 
/puppet/v3/catalog/lhcadvdeveye05.fixnetix.com?environment=production 
HTTP/1.1" 200 612 10.20.25.83 10.20.25.83 8140 249
10.20.25.83 - - - 27/Sep/2019:16:06:45 + "PUT 
/puppet/v3/report/lhcadvdeveye05.fixnetix.com?environment=production& 
HTTP/1.1" 200 9 10.20.25.83 10.20.25.83 8140 92

Unfortunately, I don't see anything untoward here nor anything helpful that 
contributes to resolving the issue.

Thanks,
Dan.

On Friday, September 27, 2019 at 2:21:32 PM UTC+1, jcbollinger wrote:
>
>
>
> On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>>
>> Please see below.  Apologies, there is a lot of detail here:
>>
>> Debug: Using settings: adding file resource 'confdir': 
>> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
>> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
>>
>
> [...]
>
> If the (elided) log messages presented were *all* the log messages 
> emitted, then they depict the agent applying an empty catalog, which is of 
> course consistent with not changing anything.  All the resources shown are 
> generated locally by the agent.  You should be able to confirm that by 
> looking at the catalog itself, which you will find, by default, in a file 
> in /opt/puppetlabs/puppet/cache/client_data/catalog.
>
> If you're making changes to your manifest set but not seeing any effect at 
> the agent then there are several possibilities, but the most likely issue 
> is server-side caching.  Before tweaking the cache configuration, however, 
> the easiest way to test this hypothesis is to flush the cache by restarting 
> the puppetserver service on the master.  (That's not the only way, but it's 
> quick and easy, and you don't need to learn anything new to do it.)
>
> If that indeed solves the problem then you'll want to adjust the 
> environment_timeout 
>  
> configuration setting on the master.  For the time being, I would suggest 
> setting it to 0 to disable caching altogether.  This is also supposed to be 
> the default if the setting is not explicitly specified, however.
>
> ---
>
> If that doesn't turn out to be the issue, then do have a look at the 
> master's logs.  You should confirm that it is logging catalog requests from 
> the agent in question (else they must be going to a different master), and 
> you should look for any messages providing a clue about the issue.  It may 
> be helpful to turn up puppetserver's log level to get more detailed 
> information.
>
> If that's also unavailing then my last suggestion would be to confirm that 
> the puppetserver process can successfully access everything in the 
> environment directory.  Check file ownership, mode, ACLs, SELinux context, 
> and anything else that affects whether the puppetserver can read the files 
> and traverse (all) the directories.  I would pay special attention to your 
> one manifest file, because that's the most likely one to be messed up in 
> this regard.
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/558c4849-87b4-41d9-b5a7-97e3e7e0896c%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[jcbollinger]

On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>
> Please see below.  Apologies, there is a lot of detail here:
>
> Debug: Using settings: adding file resource 'confdir': 
> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
>

[...]

If the (elided) log messages presented were *all* the log messages emitted, 
then they depict the agent applying an empty catalog, which is of course 
consistent with not changing anything.  All the resources shown are 
generated locally by the agent.  You should be able to confirm that by 
looking at the catalog itself, which you will find, by default, in a file 
in /opt/puppetlabs/puppet/cache/client_data/catalog.

If you're making changes to your manifest set but not seeing any effect at 
the agent then there are several possibilities, but the most likely issue 
is server-side caching.  Before tweaking the cache configuration, however, 
the easiest way to test this hypothesis is to flush the cache by restarting 
the puppetserver service on the master.  (That's not the only way, but it's 
quick and easy, and you don't need to learn anything new to do it.)

If that indeed solves the problem then you'll want to adjust the 
environment_timeout 
 
configuration setting on the master.  For the time being, I would suggest 
setting it to 0 to disable caching altogether.  This is also supposed to be 
the default if the setting is not explicitly specified, however.

---

If that doesn't turn out to be the issue, then do have a look at the 
master's logs.  You should confirm that it is logging catalog requests from 
the agent in question (else they must be going to a different master), and 
you should look for any messages providing a clue about the issue.  It may 
be helpful to turn up puppetserver's log level to get more detailed 
information.

If that's also unavailing then my last suggestion would be to confirm that 
the puppetserver process can successfully access everything in the 
environment directory.  Check file ownership, mode, ACLs, SELinux context, 
and anything else that affects whether the puppetserver can read the files 
and traverse (all) the directories.  I would pay special attention to your 
one manifest file, because that's the most likely one to be messed up in 
this regard.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/bd705228-5459-43c6-9032-104dace92dee%40googlegroups.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

No.  I only have 
/etc/puppetlabs/code/environments/production/manifests/site.pp

On Friday, September 27, 2019 at 1:03:20 PM UTC+1, Dirk Heinrichs wrote:
>
> Am Freitag, den 27.09.2019, 11:50 + schrieb Dirk Heinrichs:
>
> Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:
>
> This file does nothing.  All the lines therein are commented out.  In 
> fact, I have in the past moved this file out of the way then put it back 
> just to rule out it was doing anything weird.
>
>
> OK, just wanted to make sure it doesn't contain any strange configuration 
> for that environment. Not sure what else could be the problem. Could you 
> run the agent with --debug and post the relevant lines involving your user 
> resource (if any)?
>
>
> Oh, and do you, by chance, have a file 
> /etc/puppetlabs/code/manifests/site.pp? Mine has just the following content 
> (might as well be empty):
>
> # site.pp must exist (puppet #15106, foreman #1708)
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4a476fc2-2daf-493f-9767-dee4bcb70576%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Please see below.  Apologies, there is a lot of detail here:

Debug: Using settings: adding file resource 'confdir': 
'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'codedir': 
'File[/etc/puppetlabs/code]{:path=>"/etc/puppetlabs/code", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'vardir': 
'File[/opt/puppetlabs/puppet/cache]{:path=>"/opt/puppetlabs/puppet/cache", 
:owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'logdir': 
'File[/var/log/puppetlabs/puppet]{:path=>"/var/log/puppetlabs/puppet", 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statedir': 
'File[/opt/puppetlabs/puppet/cache/state]{:path=>"/opt/puppetlabs/puppet/cache/state",
 
:mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'rundir': 
'File[/var/run/puppetlabs]{:path=>"/var/run/puppetlabs", :mode=>"755", 
:owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'libdir': 
'File[/opt/puppetlabs/puppet/cache/lib]{:path=>"/opt/puppetlabs/puppet/cache/lib",
 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hiera_config': 
'File[/etc/puppetlabs/puppet/hiera.yaml]{:path=>"/etc/puppetlabs/puppet/hiera.yaml",
 
:ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'preview_outputdir': 
'File[/opt/puppetlabs/puppet/cache/preview]{:path=>"/opt/puppetlabs/puppet/cache/preview",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'certdir': 
'File[/etc/puppetlabs/puppet/ssl/certs]{:path=>"/etc/puppetlabs/puppet/ssl/certs",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'ssldir': 
'File[/etc/puppetlabs/puppet/ssl]{:path=>"/etc/puppetlabs/puppet/ssl", 
:mode=>"771", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'publickeydir': 
'File[/etc/puppetlabs/puppet/ssl/public_keys]{:path=>"/etc/puppetlabs/puppet/ssl/public_keys",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'requestdir': 
'File[/etc/puppetlabs/puppet/ssl/certificate_requests]{:path=>"/etc/puppetlabs/puppet/ssl/certificate_requests",
 
:mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatekeydir': 
'File[/etc/puppetlabs/puppet/ssl/private_keys]{:path=>"/etc/puppetlabs/puppet/ssl/private_keys",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'privatedir': 
'File[/etc/puppetlabs/puppet/ssl/private]{:path=>"/etc/puppetlabs/puppet/ssl/private",
 
:mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostcert': 
'File[/etc/puppetlabs/puppet/ssl/certs/lhcadvdeveye05.fixnetix.com.pem]{:path=>"/etc/puppetlabs/puppet/ssl/certs/lhcadvdeveye05.fixnetix.com.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostprivkey': 
'File[/etc/puppetlabs/puppet/ssl/private_keys/lhcadvdeveye05.fixnetix.com.pem]{:path=>"/etc/puppetlabs/puppet/ssl/private_keys/lhcadvdeveye05.fixnetix.com.pem",
 
:mode=>"640", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'localcacert': 
'File[/etc/puppetlabs/puppet/ssl/certs/ca.pem]{:path=>"/etc/puppetlabs/puppet/ssl/certs/ca.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hostcrl': 
'File[/etc/puppetlabs/puppet/ssl/crl.pem]{:path=>"/etc/puppetlabs/puppet/ssl/crl.pem",
 
:mode=>"644", :owner=>"root", :ensure=>:file, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statefile': 
'File[/opt/puppetlabs/puppet/cache/state/state.yaml]{:path=>"/opt/puppetlabs/puppet/cache/state/state.yaml",
 
:mode=>"660", :ensure=>:file, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: ad

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Freitag, den 27.09.2019, 11:50 + schrieb Dirk Heinrichs:

Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:

This file does nothing.  All the lines therein are commented out.  In fact, I 
have in the past moved this file out of the way then put it back just to rule 
out it was doing anything weird.

OK, just wanted to make sure it doesn't contain any strange configuration for 
that environment. Not sure what else could be the problem. Could you run the 
agent with --debug and post the relevant lines involving your user resource (if 
any)?

Oh, and do you, by chance, have a file /etc/puppetlabs/code/manifests/site.pp? 
Mine has just the following content (might as well be empty):

# site.pp must exist (puppet #15106, foreman #1708)

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/df404847db203d12ac6374f9876c8a6a1db64c16.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Freitag, den 27.09.2019, 03:43 -0700 schrieb Dan Crisp:

This file does nothing.  All the lines therein are commented out.  In fact, I 
have in the past moved this file out of the way then put it back just to rule 
out it was doing anything weird.

OK, just wanted to make sure it doesn't contain any strange configuration for 
that environment. Not sure what else could be the problem. Could you run the 
agent with --debug and post the relevant lines involving your user resource (if 
any)?

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c7f180603abc390a27d88a494bd172675a6d4e28.camel%40opentext.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

This file does nothing.  All the lines therein are commented out.  In fact, 
I have in the past moved this file out of the way then put it back just to 
rule out it was doing anything weird.

Dan.

On Friday, September 27, 2019 at 10:58:49 AM UTC+1, Dirk Heinrichs wrote:
>
> Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:
>
> /etc/puppetlabs/code/environments/production:
> total 20
> -rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
>
>
> What does this one contain? I don't have these in my environments.
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d431a657-2a6c-4c19-9eb1-46298447d025%40googlegroups.com.

Re: [EXTERNAL] - [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:

/etc/puppetlabs/code/environments/production:
total 20
-rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf

What does this one contain? I don't have these in my environments.

Bye...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9df7ad5e0e508fd9e4767896d50fd884a1b1ebe2.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Thank you Dirk.  However the same issue persists.  I even intentionally 
updated the site.pp with invalid syntax hoping that consequently, the agent 
run would fail and through a error.  The site.pp was updated like so:

node default {}
  include accounts
}
}

Agent still runs:

# puppet agent --no-daemonize --verbose --onetime
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Caching catalog for lhcadvdeveye05.xxx.com
Info: Applying configuration version '1569503223'
Notice: Applied catalog in 0.15 seconds




On Friday, September 27, 2019 at 10:22:56 AM UTC+1, Dirk Heinrichs wrote:
>
> Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:
>
> node 'default' {
>
>
> Should be "node default {"
>
> HTH...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhei...@opentext.com 
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4995e256-5300-49a7-bebc-1629b7c3f20a%40googlegroups.com.

[Puppet Users] ‘Contains’ conditional operator in PQL?

[Daniel Sung]

Hello,

I have a fact that is an array of strings and I would like to return all 
certnames that contain an element in that array. I’ve tried to use the in 
operator but that doesn’t work that way around and ~ does sort of work but 
it’ll match a substring of an element in the array. What is the best way to 
perform such a query?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/43ee89fd-fbf5-4873-8971-c8f538aaf5fc%40googlegroups.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dirk Heinrichs]

Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:

node 'default' {

Should be "node default {"

HTH...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/666a3429b694987ce498b1b573eb763d2653015e.camel%40opentext.com.

Re: [Puppet Users] Puppet agent is not applying changes

[Dan Crisp]

Hello Josh,

Thanks for the reply.  Still no luck I'm afraid after changing what you 
suggested.  I even changed node to be fqdn (quoted & unquoted) and that 
didn't work either.  Which again makes me think, for some reason, it's not 
being read due to perhaps being the the wrong place.

Thanks,
Dan.


On Thursday, September 26, 2019 at 7:13:48 PM UTC+1, Josh Cooper wrote:
>
> Hi Dan,
>
> I think the problem is that default should not be quoted (see 
> https://puppet.com/docs/puppet/latest/lang_node_definitions.html#syntax):
>
> If you do node "default", then puppet will only apply the class if the 
> node's fqdn is "default".
>
> Josh
>
> On Thu, Sep 26, 2019 at 9:55 AM Dan Crisp > 
> wrote:
>
>> Hello all,
>>
>> Been at this problem I have for nearly a week now and it's driving 
>> crazy!!!  I hope it's simply a case of someone with some fresh eyes taking 
>> a look and showing me the error of my ways.  
>>
>> Before I continue with the Puppet deployment, for testing purposes, I 
>> just want to create a single user namely djc72uk on a single server.  The 
>> servers name is lhcadvdeveye05 and you can see below that it has 
>> successfully generated a certificate:
>>
>> # puppetserver ca list --all
>> Signed Certificates:
>> lhcadvdeveye05.x.com   (SHA256)  
>> F1:07:CD:17:8F:0B:B5:AF:79:8A:13:F3:BA:CA:90:1A:1D:67:2C:74:C2:7F:25:3B:88:E9:34:C5:FB:50:CD:7D
>> puppet.fixnetix.com   (SHA256)  
>> 7D:2E:79:6D:DE:97:A7:B0:5D:EB:48:37:3D:B1:0F:B2:C3:E1:7F:ED:70:D9:EC:2D:71:BE:53:4A:7C:9B:B6:81
>>   
>>  alt names: ["DNS:puppet", "DNS:puppet.xx.com"]
>>
>> I'm seeing the following output from the servers when I run the agent:
>>
>> # puppet agent --no-daemonize --verbose --onetime
>> Info: Using configured environment 'production'
>> Info: Retrieving pluginfacts
>> Info: Retrieving plugin
>> Info: Retrieving locales
>> Info: Caching catalog for lhcadvdeveye05.xx.com
>> Info: Applying configuration version '1569503223'
>> Notice: Applied catalog in 0.24 seconds
>>
>> Looks all good here other than it's not applying the module I created 
>> namely accounts (see below within the puppet environment).
>>
>> *Puppet Server Environment*:
>>
>> # puppet config print confdir
>> /etc/puppetlabs/puppet
>>
>> # ll /etc/puppetlabs/puppet
>> total 48
>> drwxr-xr-x. 1 puppet puppet 4096 Sep 25 22:34 ./
>> drwxr-xr-x. 1 root   root   4096 Sep 24 12:16 ../
>> -rw-r--r--. 1 puppet puppet 5487 Sep 23 22:22 auth.conf
>> -rw-r--r--. 1 puppet puppet  161 Sep 23 22:22 hiera.yaml
>> -rw-r--r--. 1 puppet puppet  697 Sep 25 22:34 puppet.conf
>>
>> # more /etc/puppetlabs/puppet/puppet.conf
>> [master]
>> vardir = /opt/puppetlabs/server/data/puppetserver
>> logdir = /var/log/puppetlabs/puppetserver
>> rundir = /var/run/puppetlabs/puppetserver
>> pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
>> codedir = /etc/puppetlabs/code
>> environmentpath = $codedir/environments
>> autosign = true
>>
>> # puppet config print codedir
>> /etc/puppetlabs/code
>>
>> # puppet config print environmentpath
>> /etc/puppetlabs/code/environments
>>
>> # puppet config print modulepath
>>
>> /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules
>>
>> # puppet module list --tree
>> /etc/puppetlabs/code/environments/production/modules
>> └── accounts (???)
>> /etc/puppetlabs/code/modules (no modules installed)
>> /opt/puppetlabs/puppet/modules (no modules installed)
>>
>> # puppet config print manifest
>> /etc/puppetlabs/code/environments/production/manifests
>>
>> # ls -lR /etc/puppetlabs/code
>> /etc/puppetlabs/code:
>> total 8
>> drwxr-xr-x. 3 root root 4096 Sep 25 21:02 environments
>> drwxr-xr-x. 2 root root 4096 Sep 25 21:02 modules
>>
>> /etc/puppetlabs/code/environments:
>> total 4
>> drwxr-xr-x. 5 root root 4096 Sep 25 20:47 production
>>
>> /etc/puppetlabs/code/environments/production:
>> total 20
>> -rw-r--r--. 1 root root  808 Sep 25 20:47 environment.conf
>> -rw-r--r--. 1 root root  518 Sep 17 22:22 hiera.yaml
>> drwxr-xr-x. 2 root root 4096 Sep 24 20:34 manifests
>> drwxr-xr-x. 3 root root 4096 Sep 24 19:57 modules
>>
>>
>> /etc/puppetlabs/code/environments/production/manifests:
>> total 4
>> -rw-r--r--. 1 root root 40 Sep 24 20:34 site.pp
>>
>> /etc/puppetlabs/code/environments/production/modules:
>> total 4
>> drwxr-x---. 5 root root 4096 Sep 25 21:18 accounts
>>
>> /etc/puppetlabs/code/environments/production/modules/accounts:
>> total 12
>> drwxr-x---. 2 root root 4096 Sep 24 20:38 manifests
>>
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests:
>> total 8
>> -rw-r-. 1 root root  77 Sep 24 20:38 groups.pp
>> -rw-r-. 1 root root 224 Sep 24 20:01 init.pp
>>
>> /etc/puppetlabs/code/modules:
>> total 0
>>
>> # more /etc/puppetlabs/code/environments/production/manifests/site.pp
>> node 'default' {
>>   include accounts
>> }
>>
>> # more 
>> /etc/puppetlabs/code/environments/production/modules/accounts/manifests/init.pp
>>