Re: [Puppet Users] Removal of CentOS 8 Support

[Peter Meier]

Hi

Great questions! I'm adding Margaret Lee, one of our Product Managers, 
to help get your questions answered. She'll be back from PTO on Monday! 
Thanks.


Just to re-iterate what I brought up a few months ago: It would be very 
welcoming, when Puppet ships at least a "supported" agent (or at least 
an installable as preview) as early as possible for CentOS Stream 9.


This would allow other communities (e.g. voxpupuli 
(https://github.com/voxpupuli/beaker-hostgenerator/pull/225), etc.) to 
start working on supporting CentOS Stream 9 as early as possible and 
thus would also likely help to boost adoption of puppet within RHEL 9 
environments and also keep it in place for folks who are upgrading to EL 9.


From a technical perspective, it is likely similar to how the agent is 
bundled for Fedora 34 / 35 - so I don't see a lot to be done for a dev 
preview.


~pete

--
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/4728fe4d-e65a-920b-4f71-b47a3f7f3dd4%40immerda.ch.

Re: [Puppet Users] Removal of CentOS 8 Support

[Peter Meier]

Hi All,

This is an announcement that we’ll be removing support for CentOS 8 in 
February 2022 because CentOS 8 is EOLed from the vendor in December 
2021. For a list of other supported operating systems for your primary 
server, see the supported operating systems 
docs. 


Are you going to add CentOS Stream 8, Alma Linux 8 and Rocky Linux 8 ?

Given all of them are RHEL 8 based (Stream 8 just tracking ahead, but 
still it's RHEL 8), I would expect it to just work. But Since CentOS 8 
was officially supported what needs to be done to get these EL 8 
releases to the same level?


~pete

--
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/0f2882b8-f6c3-b7ee-08d5-8ecbdd36c00c%40immerda.ch.

Re: [Puppet Users] Newbie wants to know your favourite distro for Puppet Server

[Peter Meier]

On 17.06.21 02:58, Ian Mortimer wrote:
> On Wed, 2021-06-16 at 05:44 -0700, Jarod Schoen wrote:
> 
>> I went CentOS 7.9 because some body of people is saying that version
>> 8 is beleaguered already... I dont know who to believe.
> 
> You probably don't want to install CentOS 8 on any production server. 
> It will be replaced at the end of the year by CentOS Stream:
> 
>https://www.centos.org/centos-stream/
> 
> If you want to stay RedHat based, Oracle Linux would be the safest
> option currently.

Or you just don't believe the FUD spread all over the internet and you
go with CentOS Stream 8 already now, which is the same as CentOS Linux
just a bit earlier available (even earlier than Oracle, Rocky, ...).

I happily converted all my CentOS Linux 8 Systems (close to 100) to
CentOS Stream 8 last year and it all works fine. There is zero difference.

I am also looking forward to start integrating CentOS Stream 9 in the
next few months, which means I'll be able to start planning and
integrating the next version way before Oracle even gets to rebuild it.

~pete

-- 
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/be1545f0-40dd-caf2-0c70-22b3f86c0324%40immerda.ch.

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

[Peter Meier]

Hi Josh,

> All resolved issues should be available in nightly puppet7 builds, such
> as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm
> .
> It'd be great to get confirmation in the next few days that these issues
> are in fact fixed.

Unfortunately, the EL 7 nightly repo wants to install el8 content, which
is a) wrong and b) is not found in the repo. See below.

So I installed the rpm directly:

yum update
http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el7.x86_64.rpm


Which worked and I confirmed in the ticket that this fixes the issue.

~pete

# grep puppet /etc/yum.repos.d/*
/etc/yum.repos.d/puppet7-nightly.repo:[puppet7-nightly]
/etc/yum.repos.d/puppet7-nightly.repo:baseurl=http://nightlies.puppet.com/yum/puppet7-nightly/el/7/$basearch
/etc/yum.repos.d/puppet7-nightly.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet7-nightly-release
/etc/yum.repos.d/puppet.repo:[puppet]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/$basearch
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release
/etc/yum.repos.d/puppet.repo:[puppet-source]
/etc/yum.repos.d/puppet.repo:baseurl=https://yum.puppetlabs.com/puppet/el/7/SRPMS
/etc/yum.repos.d/puppet.repo:gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-release

# rpm -qf /etc/yum.repos.d/puppet7-nightly.repo
puppet7-nightly-release-1.0.0-2.el7.noarch

# yum update --disablerepo=puppet
Loaded plugins: fastestmirror, priorities
Repository base is listed more than once in the configuration
Repository centosplus is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: mirror.imt-systems.com
 * centos7-plus: centos.bio.lmu.de
 * epel: mirrors.ircam.fr
 * extras: linuxsoft.cern.ch
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.imt-systems.com
939 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package puppet-agent.x86_64 0:7.0.0-1.el7 will be updated
---> Package puppet-agent.x86_64 0:7.0.0.103.gf0655d02-1.el8 will be an
update
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el7 will be updated
---> Package puppet7-nightly-release.noarch 0:1.0.0-2.el8 will be an update
--> Finished Dependency Resolution

Dependencies Resolved


 Package   Arch Version
Repository Size

Updating:
 puppet-agent  x86_64
7.0.0.103.gf0655d02-1.el8   puppet7-nightly24 M
 puppet7-nightly-release   noarch   1.0.0-2.el8
puppet7-nightly14 k

Transaction Summary

Upgrade  2 Packages

Total download size: 25 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for puppet7-nightly
puppet7-nightly-release-1.0.0- FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet7-nightly-release-1.0.0-2.el8.noarch.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use
https://bugs.centos.org/.

puppet-agent-7.0.0.103.gf0655d FAILED

http://nightlies.puppet.com/yum/puppet7-nightly/el/7/x86_64/puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64.rpm:
[Errno 14] HTTP Error 404 - Not Found
Trying other mirror.


Error downloading packages:
  puppet7-nightly-release-1.0.0-2.el8.noarch: [Errno 256] No more
mirrors to try.
  puppet-agent-7.0.0.103.gf0655d02-1.el8.x86_64: [Errno 256] No more
mirrors to try.

-- 
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/cb882c56-58ab-54e3-4b42-7c06750e8747%40immerda.ch.

Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

[Peter Meier]

Hi All,

> Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet'
> repos to point to the new 'puppet7' release from a couple of weeks ago.
> If you're already using the 'puppet' release packages (such
> as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm
> ), your repos
> will start pointing to puppet7 tomorrow.


Anybody having VMs / Baremetals / ... using VLANs: You will run into a
regression with Facter 4 that will stop puppet 7 from working on these
machines:

https://tickets.puppetlabs.com/browse/FACT-2870

The fix is there, but there is no release yet containing the fix. So
it's worth holding these machines of from being updated on the rolling
repos.

Additionally, there are a couple of regressions regarding how networking
facts are being reported by Facter 4:

https://tickets.puppetlabs.com/browse/FACT-2871
https://tickets.puppetlabs.com/browse/FACT-2872

If you are depending on these facts in your manifests (e.g. in a
condition), it might be the case that puppet will do something
differently. I suggest checking your manifests for the usage of these facts.

I didn't check the bug tracker thoroughly for other regressions, but I
have seen a few more. So it might worth looking into it, as regressions
in fact reporting can have unintended side-effects.

And really only cosmetic wise, you get a bunch of warnings in puppet 7
for the user and exec types:

https://tickets.puppetlabs.com/browse/MODULES-10876
https://tickets.puppetlabs.com/browse/PUP-10790

They are not really an issue, but might affect you if you are parsing
the output. E.g. filtering cron output -> cron emails are sent out with
these alerts.

Other than that: Puppet 7 runs smoothly, be sure to re-install your
gems, as it switches to Ruby 2.7

best

~pete

-- 
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/354bd76b-c85c-3026-9906-b7c3d20adf3b%40immerda.ch.

Re: [Puppet Users] Issue with puppet6 release packages

[Peter Meier]

>   * If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless
> you want to be subscribed to the repo with rolling updates, you
> should uninstall and reinstall the release package.
>   * If /etc/yum.repos.d/puppet6.repo exists -- you are not affected.

So what is the intend for rolling updates?

Given https://yum.puppetlabs.com/puppet/el/7/x86_64/ does not anymore
contain the 7.0.0 release although it did for a while.

~pete

-- 
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/34c6750c-48f4-5b0a-951b-1e1a5cedcbc7%40immerda.ch.

Re: [Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'

[Peter Krawetzky]

Ok I figured out the curl command but I get this error:

[root@mypuppetserver private_keys]# curl -v --header "Content-Type: 
application/json" --cert 
/etc/puppetlabs/puppet/ssl/certs/mypuppetserver.mydomain.com.pem 
--key 
/etc/puppetlabs/puppet/ssl/private_keys/mypuppetserver.mydomain.com.pem 
--cacert
/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem -X DELETE 
https://mypuppetserver.mydomain.com:8140/puppet-admin-api/v1/environment-cache
* About to connect() to mypuppetserver.mydomain.com port 8140 (#0)
*   Trying xx.xx.xxx.xx...
* Connected to mypuppetserver.mydomain.com (xx.xx.xxx.xx) port 8140 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem
  CApath: none
* NSS: client certificate from file
*   subject: CN=mypuppetserver.mydomain.com
*   start date: Aug 14 15:32:34 2018 GMT
*   expire date: Aug 14 15:32:34 2023 GMT
*   common name: mypuppetserver.mydomain.com
*   issuer: CN=Puppet CA: mypuppetcaserver.mydomain.com
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
*   subject: CN=mypuppetserver.mydomain.com
*   start date: Aug 14 15:32:34 2018 GMT
*   expire date: Aug 14 15:32:34 2023 GMT
*   common name: mypuppetserver.mydomain.com
*   issuer: CN=Puppet CA: mypuppetcaserver.mydomain.com
> DELETE /puppet-admin-api/v1/environment-cache HTTP/1.1
> User-Agent: curl/7.29.0
> Host: mypuppetserver.mydomain.com:8140
> Accept: */*
> Content-Type: application/json
>
< HTTP/1.1 403 Forbidden
< Date: Fri, 17 Jul 2020 13:41:37 GMT
< Content-Length: 115
< Server: Jetty(9.4.z-SNAPSHOT)
<
* Connection #0 to host mypuppetserver.mydomain.com left intact
Forbidden request: /puppet-admin-api/v1/environment-cache (method :delete). 
Please see the server logs for details.[root@mypuppetserver private_keys]#

*puppetserver.log entries*:
2020-07-17 09:07:45,577 ERROR [qtp2067827614-66] [p.t.a.rules] Forbidden 
request: 0:0:0:0:0:0:0:1 access to /puppet-admin-api/v1/environment-cache 
(method :delete) (authenticated: false) denied by rule 'puppetlabs deny 
all'.
2020-07-17 09:07:45,585 ERROR [qtp2067827614-65] [p.t.a.rules] Forbidden 
request: 0:0:0:0:0:0:0:1 access to /puppet-admin-api/v1/environment-cache 
(method :delete) (authenticated: false) denied by rule 'puppetlabs deny 
all'.
2020-07-17 09:12:02,951 ERROR [qtp2067827614-63] [p.t.a.rules] Forbidden 
request: xx.xx.xxx.xx access to /puppet-admin-api/v1/environment-cache 
(method :delete) (authenticated: false) denied by rule 'puppetlabs deny 
all'.
2020-07-17 09:17:29,677 ERROR [qtp2067827614-61] [p.t.a.rules] Forbidden 
request: xx.xx.xxx.xx access to /puppet-admin-api/v1/environment-cache 
(method :delete) (authenticated: false) denied by rule 'puppetlabs deny 
all'.
2020-07-17 09:41:37,401 ERROR [qtp2067827614-63] [p.t.a.rules] Forbidden 
request: mypuppetserver.mydomain.com(xx.xx.xxx.xx) access to 
/puppet-admin-api/v1/environment-cache (method :delete) (authenticated: 
true) denied by rule 'puppetlabs deny all'.

-- 
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/173aa581-ddde-4e2a-aa46-b9666f93e844o%40googlegroups.com.

Re: [Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'

[Peter Krawetzky]

Does this work for Open Source or PE?  My installation is using Open Source.

Also can you provide an example of the actual curl command?  I can't seem 
to get the exact syntax down for it to work.  

Thanks for the advice.

On Thursday, July 16, 2020 at 7:55:51 PM UTC-4, Justin Stoller wrote:
>
> It maybe because of a long environment timeout: 
> https://puppet.com/docs/puppet/5.5/environments_creating.html#task-3930
> In PE this is set to unlimited by default when using code management. The 
> code manager will then manually evict the cache after a code deployment to 
> ensure that new code is viewable and old code is cached for as long as 
> possible. If you are caching code with a long environment timeout, but not 
> using code management you can also evict the cache by using the 
> environment-cache endpoint:
>
> https://puppet.com/docs/puppetserver/latest/admin-api/v1/environment-cache.html
>
>  HTH, 
> Justin
>
> On Thu, Jul 16, 2020 at 10:52 AM Peter Krawetzky  > wrote:
>
>> I've reviewed sever 500 error posts in here but the answers seem to 
>> differ based on the situation.
>>
>>
>> One of our developers modified code to include a parameter available in 
>> httpfile 0.1.9 called quick_check.  
>>
>> We have two installation of puppetserver one in lab domain and one in 
>> production domain.  Neither talk to the other domain.  It is completely 
>> isolated to the nodes in each domain.
>>
>> What's odd is lab works but when they deploy the code to production, it 
>> doesn't work and received the 500 error below.  I've compared everything 
>> between puppetserver versions, puppet versions, httpfile module versions, 
>> etc and nothing is obvious.
>>
>>
>> This httpfile module is not installed using puppet module install but is 
>> placed in the same location as other modules created by the developers.
>>
>> I've verified the code was deployed correctly to each of the 4 production 
>> puppetservers (we use a load balancer to distribute the work) into the 
>> environment defined at the node (dev).
>>
>>
>> Code:
>> ### DOWNLOAD FROM REPO
>> define oracle::remote_file($remote_location=undef, $mode='0644', $owner='
>> root', $group='root'){
>>
>> httpfile { "${title}":
>> ensure => present,
>> path => "${title}",
>> source => "$remote_location",
>> quick_check => true,
>> # hash => 'hex form SHA2 hash OR an URL to the .sha file with that hash'
>> }
>> file{$title:
>> owner => $owner,
>> group => $group,
>> mode => $mode,
>> require => Httpfile["${title}"],
>> }
>> }
>>
>>
>> Error:
>>
>> 2020-07-15T08:35:15.325976-04:00 myserver puppet-agent[24036]: Could not 
>> retrieve catalog from remote server: Error 500 on SERVER: Server Error: no 
>> parameter named 'quick_check' (file: 
>> /u01/puppet/dev/modules/oracle/manifests/remote_file.pp, line: 6) on 
>> Httpfile[/var/opt/BESClient/LMT/oracle/options_packs_usage_statistics.sql] 
>> (file: /u01/puppet/dev/modules/oracle/manifests/remote_file.pp, line: 6) on 
>> node myserver.mydomain.com
>>
>>
>> Any ideas what might be causing this?  Is there some cache not being 
>> refreshed on the pupperserver?
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/886fd9da-c841-4d8b-80f3-d23bc2429e68o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/886fd9da-c841-4d8b-80f3-d23bc2429e68o%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/506125c9-66df-4f67-84fc-1a10b1b137dbo%40googlegroups.com.

[Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'

[Peter Krawetzky]

I've reviewed sever 500 error posts in here but the answers seem to differ 
based on the situation.


One of our developers modified code to include a parameter available in 
httpfile 0.1.9 called quick_check.  

We have two installation of puppetserver one in lab domain and one in 
production domain.  Neither talk to the other domain.  It is completely 
isolated to the nodes in each domain.

What's odd is lab works but when they deploy the code to production, it 
doesn't work and received the 500 error below.  I've compared everything 
between puppetserver versions, puppet versions, httpfile module versions, 
etc and nothing is obvious.


This httpfile module is not installed using puppet module install but is 
placed in the same location as other modules created by the developers.

I've verified the code was deployed correctly to each of the 4 production 
puppetservers (we use a load balancer to distribute the work) into the 
environment defined at the node (dev).


Code:
### DOWNLOAD FROM REPO
define oracle::remote_file($remote_location=undef, $mode='0644', $owner='
root', $group='root'){

httpfile { "${title}":
ensure => present,
path => "${title}",
source => "$remote_location",
quick_check => true,
# hash => 'hex form SHA2 hash OR an URL to the .sha file with that hash'
}
file{$title:
owner => $owner,
group => $group,
mode => $mode,
require => Httpfile["${title}"],
}
}


Error:

2020-07-15T08:35:15.325976-04:00 myserver puppet-agent[24036]: Could not 
retrieve catalog from remote server: Error 500 on SERVER: Server Error: no 
parameter named 'quick_check' (file: 
/u01/puppet/dev/modules/oracle/manifests/remote_file.pp, line: 6) on 
Httpfile[/var/opt/BESClient/LMT/oracle/options_packs_usage_statistics.sql] 
(file: /u01/puppet/dev/modules/oracle/manifests/remote_file.pp, line: 6) on 
node myserver.mydomain.com


Any ideas what might be causing this?  Is there some cache not being 
refreshed on the pupperserver?

-- 
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/886fd9da-c841-4d8b-80f3-d23bc2429e68o%40googlegroups.com.

[Puppet Users] Re: hiera v3 to v5 with puppet apply

[Peter Dutton]

I've figured this out now - I was mistakenly using hiera.yaml to store the 
data values. Once I changed it to refer to a different file for the data it 
was running fine.

Thanks

Peter

On Monday, 15 June 2020 17:04:45 UTC+1, Peter Dutton wrote:
>
> Hi all,
>
> I am using puppet in a 'standalone', or 'masterless' capacity to manage 
> the configurations of different server roles. I'm doing this by using 
> 'puppet apply' with a different environment depending on the situation. For 
> example for local development:
>
> puppet apply --modulepath=modules --hiera_config=environments/hiera.yaml 
> --environment=devLocal manifests/init.pp
>
>
> I'm upgrading the infrastructure and am having trouble converting my 
> workflow to the newer version. I have converted the hiera() function calls 
> to lookup(), and have moved logic around in the hiera.yaml files so that 
> now it should be processing the correct file when the command runs. 
>
>
> However I currently get an error for each hiera variable, for example: 
> "The Lookup Configuration at 
> '/tmp/vagrant-puppet/environments/devLocal/hiera.yaml' has wrong type, 
> unrecognized key 'server_role'"
>
> The file itself (reduced for simplicity) looks as follows 
> (environments/devLocal/hiera.yaml):
>
>
> version: 5
>
>
> server_role: "frontend"
>
>
>
> The code in environments/hiera.yaml is as follows:
>
> version: 5
>
>
> defaults:
>   datadir: "environments"
>   data_hash: yaml_data
>
>
> hierarchy:
>   - name: "env"
> path: "%{environment}/hiera.yaml"
>
>
>
>
> Does anyone have any suggestions on how I can make this work?
>

-- 
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/c75bf49c-fde5-4e96-a546-504ceea4e476o%40googlegroups.com.

[Puppet Users] hiera v3 to v5 with puppet apply

[Peter Dutton]

Hi all,

I am using puppet in a 'standalone', or 'masterless' capacity to manage the 
configurations of different server roles. I'm doing this by using 'puppet 
apply' with a different environment depending on the situation. For example 
for local development:

puppet apply --modulepath=modules --hiera_config=environments/hiera.yaml --
environment=devLocal manifests/init.pp


I'm upgrading the infrastructure and am having trouble converting my 
workflow to the newer version. I have converted the hiera() function calls 
to lookup(), and have moved logic around in the hiera.yaml files so that 
now it should be processing the correct file when the command runs. 


However I currently get an error for each hiera variable, for example: "The 
Lookup Configuration at 
'/tmp/vagrant-puppet/environments/devLocal/hiera.yaml' has wrong type, 
unrecognized key 'server_role'"

The file itself (reduced for simplicity) looks as follows 
(environments/devLocal/hiera.yaml):


version: 5


server_role: "frontend"



The code in environments/hiera.yaml is as follows:

version: 5


defaults:
  datadir: "environments"
  data_hash: yaml_data


hierarchy:
  - name: "env"
path: "%{environment}/hiera.yaml"




Does anyone have any suggestions on how I can make this work?

-- 
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/5f5bb8a3-26e9-4386-a961-be02583a885fo%40googlegroups.com.

[Puppet Users] PuppetDB Using Puppetlabs Postgresql Module on Linux

[Peter Krawetzky]

I was looking through the documentation and couldn't find my answer.  I 
want to use both the PuppetDB and Postgresql supported modules to install 
and manage both.  I don't want to use the default database directory 
"/var/lib/postgresql/..." but want to specify my own.  What do I use to 
point the database directory to another physical location?  If a different 
location is specified, does the Postgresql module correctly configure 
systemctl stop/start/restart process?

-- 
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/e01f26bb-b7cf-4d22-ab95-deb8336189b6%40googlegroups.com.

[Puppet Users] Re: Puppet Log Directory Permissions

[Peter Krawetzky]

Interesting, thanks!

On Tuesday, June 4, 2019 at 1:59:07 PM UTC-4, Peter Krawetzky wrote:
>
> I want to be able to ingest the puppet servers logs into splunk but the 
> owner of the directory is puppet:puppet and the permissions are 
> /var/log/puppetlabs/puppet rwxr-x---.  Since other has no access, the 
> splunk service will not be able to read the log files.  Can I just change 
> the permissions to rwxr-xr-x without any adverse affects to the 
> puppetserver process?  Is there a way to do this in a puppetserver config 
> file like logback.xml?
>

-- 
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/dbd9bd2a-4219-4af4-99ad-3914db993002%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Log Directory Permissions

[Peter Krawetzky]

I want to be able to ingest the puppet servers logs into splunk but the 
owner of the directory is puppet:puppet and the permissions are 
/var/log/puppetlabs/puppet rwxr-x---.  Since other has no access, the 
splunk service will not be able to read the log files.  Can I just change 
the permissions to rwxr-xr-x without any adverse affects to the 
puppetserver process?  Is there a way to do this in a puppetserver config 
file like logback.xml?

-- 
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/0c69b316-a7ff-4417-84db-eb46f92882a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB failing to start up with bizarre complaint

[Peter Berghold]

Using the puppetlabs/puppetdb module to manage PuppetDB I'm seeing way to
much red text and PuppetDB is not "refreshing" meaning restarting. It is
failing with an error message
 java.lang.IllegalArgumentException: Specified bootstrap config file does
not exist: '/etc/puppetlabs/puppetdb/bootstrap.cfg'

and yet the file is really there and contains:

# This file is used by the application framework (trapperkeeper) to
# determine what services should be loaded at boot time.
# For more info, see:
#  https://github.com/puppetlabs/trapperkeeper/wiki/Bootstrapping

# Web Server
puppetlabs.trapperkeeper.services.webserver.jetty9-service/jetty9-service

# Webrouting
puppetlabs.trapperkeeper.services.webrouting.webrouting-service/webrouting-service

# TK status
puppetlabs.trapperkeeper.services.metrics.metrics-service/metrics-webservice
puppetlabs.trapperkeeper.services.status.status-service/status-service
puppetlabs.trapperkeeper.services.scheduler.scheduler-service/scheduler-service

# PuppetDB Services
puppetlabs.puppetdb.cli.services/puppetdb-service
puppetlabs.puppetdb.command/command-service
puppetlabs.puppetdb.pdb-routing/maint-mode-service
puppetlabs.puppetdb.pdb-routing/pdb-routing-service
puppetlabs.puppetdb.config/config-service

# NREPL
puppetlabs.trapperkeeper.services.nrepl.nrepl-service/nrepl-service

# Dashboard redirect: remove to disable
puppetlabs.puppetdb.dashboard/dashboard-redirect-service

so... what is really going on here?
-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv3_t0401gqSe8WQPQgRM_LU8SjV2DEjxM3GnF4PMnFAoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] class invocation conflicts

[Peter Berghold]

Using include instead of class makes sense to me and was my instinctive
thought.

Why on earth, then, do all the (or most) of the Puppet Forge modules use
the

class{'myclass':
param1 => 'thing'
}

patterns in their examples.  I had begun to believe that was the preferred
pattern.

I will mend my ways.

On Mon, May 20, 2019 at 3:33 PM Henrik Lindberg 
wrote:

> On 2019-05-20 18:57, Peter Berghold wrote:
> > So here I am I have a base profile for my Ubuntu (Debian family)
> > machines that invokes the class
> >
> > class{'apt':
> >  ... some paramters
> > }
> >
> > I then invoke the class
> >
> > class{'postgresql': }
> >
> > and now Puppet is screaming that the class 'apt' cannot be invoked
> > twice.   This seems to be a flaw in Puppet manifests to me.  How to fix?
> >
> >
>
> The best practice is to not use the resource like `class { name: ... }`
> syntax to declare a class and instead use `include name` and letting all
> parameter values come from hiera via automatic parameter lookup.
>
> That way, you can include the class as many times as you like - as the
> parameters are the same every time. Unfortunately, the compiler cannot
> do the same when classes are declared with parameters even if all places
> this is done use the exact same values.
>
> While it is possible to have a single `class { name: ... }` declaration
> with subsequent `include name` declarations, the opposite does not work.
>
> Hope this helps.
> - henrik
>
> > --
> >
> > Peter L. Berghold salty.cowd...@gmail.com  salty.cowd...@gmail.com>
> >
> > http://devops.berghold.net
> >
> >
> > --
> > 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
> > <mailto:puppet-users+unsubscr...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/puppet-users/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com?utm_medium=email_source=footer
> >.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> 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/qbuve5%246tlm%241%40blaine.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv3dQ-t2W_0%2BNpq0qD9%2BkHAnsLXfwJtJQHxJURywdb7wZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] class invocation conflicts

[Peter Berghold]

So here I am I have a base profile for my Ubuntu (Debian family) machines
that invokes the class

class{'apt':
... some paramters
}

I then invoke the class

class{'postgresql': }

and now Puppet is screaming that the class 'apt' cannot be invoked twice.
 This seems to be a flaw in Puppet manifests to me.  How to fix?


-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet apt repository broken?

[Peter Berghold]

After 30+ years in the IT industry I'd have to say "stuff happens."

Thanks for giving it attention

On Wed, May 15, 2019 at 5:06 PM Morgan Rhodes  wrote:

> The bionic repo should be working again. Let us know if you have any more
> issues.
>
> On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes  wrote:
>
>> Hi Peter,
>>
>> Apologies, we've been having some repo issues today. I'm getting the
>> bionic repository updated now and it should be done within the hour. I will
>> send another update here when it completes.
>>
>> On Wed, May 15, 2019 at 1:43 PM Peter Berghold 
>> wrote:
>>
>>> Just this afternoon around 4PM I started noticing this happen in my
>>> Docker builds that incorporate loading the Puppet agent:
>>> W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
>>> the component 'puppet' (component misspelt in sources.list?)
>>> W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
>>> repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have
>>> the component 'puppet' (component misspelt in sources.list?)
>>> Reading package lists...
>>> Building dependency tree...
>>> Reading state information...
>>> Package puppet-agent is not available, but is referred to by another
>>> package.
>>> This may mean that the package is missing, has been obsoleted, or
>>> is only available from another source
>>>
>>> E: Package 'puppet-agent' has no installation candidate
>>>
>>> same Docker build worked swimmingly earlier today and seems broken now
>>> with NOTHING changing in the build (except to add NTP).  Any idea why this
>>> is happening and more importantly any idea when the issue will go away?
>>>
>>>
>>>
>>> --
>>>
>>> Peter L. Berghold   salty.cowd...@gmail.com
>>>
>>> http://devops.berghold.net
>>>
>>>
>>> --
>>> 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/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/puppet-users/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Morgan Rhodes
>> Release Engineering
>> mor...@puppet.com
>>
>
>
> --
> Morgan Rhodes
> Release Engineering
> mor...@puppet.com
>
> --
> 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/CA%2BFnDv05WW0i2z5sP7q0LyX65_TBR%3DiDOJYNddh%3DCAuxnaXVfA%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CA%2BFnDv05WW0i2z5sP7q0LyX65_TBR%3DiDOJYNddh%3DCAuxnaXVfA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv1-QMhHU-9-skuWcqwAfwxECEDgze95hPLkYJHQTt_Kxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet apt repository broken?

[Peter Berghold]

Just this afternoon around 4PM I started noticing this happen in my Docker
builds that incorporate loading the Puppet agent:
W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
component 'puppet' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'puppet/binary-amd64/Packages' as
repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
component 'puppet' (component misspelt in sources.list?)
Reading package lists...
Building dependency tree...
Reading state information...
Package puppet-agent is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'puppet-agent' has no installation candidate

same Docker build worked swimmingly earlier today and seems broken now with
NOTHING changing in the build (except to add NTP).  Any idea why this is
happening and more importantly any idea when the issue will go away?



-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv0TA-u%2BxM-8wxrQ9b8FOJ9ZCn_%3DBRR2bqjaimXSZm0jGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] eyaml edit ending strangly

[Peter Berghold]

OK... found one problem and have another.  I am trying to encrypt a OpenSSL
private key and of course it is multiline.

Found out that I was specifiying PKS7 at the beginning of the block and was
supposed to specify PKCS7 instead.  Old eyes I guess.

Corrected that and not have something that looks sorta like:
mykeyhere: PKCS7[
- key start -
... body of key...
...with many...
lines
 key end 
]!
but when I end the edit I see:
[hiera-eyaml-core] nested asn1 error

I seem to remember I have to do something special with multiline values in
yaml/eyaml...  but I don't remember what.


On Tue, Apr 30, 2019 at 3:16 PM Robert  wrote:

> Hi,
>
> it's probably a copy error but
>
> [hiera-eyaml-core] cannot load such file --
> hiera/backend/eyaml/encryptors/pk*s7*
>
>
> vs.
>
> hiera/backend/eyaml/encryptors/pk*cs7*.rb
>
>
> You don't have a typo in some config, do you?
>
> Best
> Rp
>
> On Mon, Apr 29, 2019 at 10:42 PM Peter Berghold 
> wrote:
>
>> I had installed hiera-eyaml on my development box.  My home laptop is set
>> up the same way (I think) and the error I'm seeing doesn't happen on that
>> box.
>>
>> When I end he edit session I'm getting:
>>
>> /usr/bin/eyaml edit common.eyaml
>> [hiera-eyaml-core] cannot load such file --
>> hiera/backend/eyaml/encryptors/pks7
>>
>> and losing my edits
>>
>> Looking through the system I find a directory:
>>
>>
>> /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hiera-eyaml-3.0.0/lib/hiera/backend
>>
>> Diggin
>> deeper:/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hiera-eyaml-3.0.0/lib/hiera/backend/eyaml/encryptors/pkcs7.rb
>>
>> and more interestingly
>> /usr/lib/ruby/vendor_ruby/hiera/backend/eyaml/encryptors/pkcs7.rb
>>
>> so... anybody have an idea why I'm seeing the error above?
>>
>>
>> -
>>
>> Peter L. Berghold   salty.cowd...@gmail.com
>>
>> http://devops.berghold.net
>>
>>
>> --
>> 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/CAArvnv0U%3D%3DtzdN6Gq0dy6K6oRHONRpqKfzkXTZkTqHMWP_LX4w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CAArvnv0U%3D%3DtzdN6Gq0dy6K6oRHONRpqKfzkXTZkTqHMWP_LX4w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CANwwCtxN-zN_SX6PhBC2%3DkqjMnEgAeT7kUg3-%2BHwLrfYWaxQig%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CANwwCtxN-zN_SX6PhBC2%3DkqjMnEgAeT7kUg3-%2BHwLrfYWaxQig%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv15Gdmb941KsaQVRSaRKDP%2B3YJTtbitzAHxFM0_8bOsrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] eyaml edit ending strangly

[Peter Berghold]

I had installed hiera-eyaml on my development box.  My home laptop is set
up the same way (I think) and the error I'm seeing doesn't happen on that
box.

When I end he edit session I'm getting:

/usr/bin/eyaml edit common.eyaml
[hiera-eyaml-core] cannot load such file --
hiera/backend/eyaml/encryptors/pks7

and losing my edits

Looking through the system I find a directory:

/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hiera-eyaml-3.0.0/lib/hiera/backend

Diggin
deeper:/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hiera-eyaml-3.0.0/lib/hiera/backend/eyaml/encryptors/pkcs7.rb

and more interestingly
/usr/lib/ruby/vendor_ruby/hiera/backend/eyaml/encryptors/pkcs7.rb

so... anybody have an idea why I'm seeing the error above?


-

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv0U%3D%3DtzdN6Gq0dy6K6oRHONRpqKfzkXTZkTqHMWP_LX4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet.el.. where did it go?

[Peter Berghold]

After updating my Ubuntu laptop I noticed the Xenial package for Puppet no
longer included the puppet-el package.  Where did it go?  I relied on it to
keep my Puppet coding more or less compliant with standards... except for
that two space indentation thing...

-- 

Peter L. Berghold   salty.cowd...@gmail.com

http://devops.berghold.net

-- 
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/CAArvnv1h7xR%3Dcs0nktkSJjrL5ruHEzJXw2Tcb0Tw6%3DrLFT9jLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Latest version of lookup_http not in rubygems.org

[Peter Krawetzky]

Yeah it looks like I did get this in reverse but it doesn't explain why an 
SSL connection is not working to couchdb.

On Tuesday, February 19, 2019 at 4:23:26 PM UTC-5, Peter Krawetzky wrote:
>
> I'm trying to an SSL connection from puppetserver to a couchdb no-sql 
> database for hiera lookup data.  I have both hiera-http and lookup_http 
> installed however the version of lookup_http.rb file that gets installed 
> from running the puppetserver gem install command is 1.0.3.  The version I 
> want to install is 1.4.0 https://github.com/crayfishx/lookup_http
>
> Is there any way I can get the 1.4.0 version installed on my 
> puppetserver?  SSL was supported in 1.2.0 so I figured I would just install 
> the latest.
>

-- 
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/3823bae5-2d21-419f-83a0-c3403d715c35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Latest version of lookup_http not in rubygems.org

[Peter Krawetzky]

I'm trying to an SSL connection from puppetserver to a couchdb no-sql 
database for hiera lookup data.  I have both hiera-http and lookup_http 
installed however the version of lookup_http.rb file that gets installed 
from running the puppetserver gem install command is 1.0.3.  The version I 
want to install is 1.4.0 https://github.com/crayfishx/lookup_http

Is there any way I can get the 1.4.0 version installed on my puppetserver?  
SSL was supported in 1.2.0 so I figured I would just install the latest.

-- 
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/70ad68b8-5fe6-42ed-a15d-85433b9e2992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PDK on bionic Ubuntu

[Peter Berghold]

David,

Removing ~/.pdk did the job.  I had already tried removing Gemfile.lock
thinking that was the issue.

Works good now. thanks


On Mon, Jan 28, 2019 at 10:53 AM David Schmitt 
wrote:

> This Gemfile works on my debian machine, which means we can exclude a
> whole bunch of potential problems. As next step, try removing your
> `Gemfile.lock` and the `/home/peter/.pdk/cache/ruby/` directory.
>
> I hope that helps.
>
> Cheers, David
>
> unrelated PS: the changes you made to require hiera 3.5.0 in the Gemfile
> do not work. It still pulls in version 3.4.5.13. I've created
> https://github.com/puppetlabs/pdk-templates/issues/182 to ask for
> allowing this to be overridden through the regular channels. At the same
> time, I'd also caution against modifying these bits too radically, as the
> PDK chooses the versions that we ship in the puppet-agent package, so
> changing that around will invalidate your test results.
>
>
> On Mon, Jan 28, 2019 at 3:21 PM Peter Berghold 
> wrote:
>
>> Gemfile
>> source ENV['GEM_SOURCE'] || 'https://rubygems.org'
>>
>> def location_for(place_or_version, fake_version = nil)
>>   git_url_regex = %r{\A(?(https?|git)[:@][^#]*)(#(?.*))?}
>>   file_url_regex = %r{\Afile:\/\/(?.*)}
>>
>>   if place_or_version && (git_url = place_or_version.match(git_url_regex))
>> [fake_version, { git: git_url[:url], branch: git_url[:branch],
>> require: false }].compact
>>   elsif place_or_version && (file_url =
>> place_or_version.match(file_url_regex))
>> ['>= 0', { path: File.expand_path(file_url[:path]), require: false }]
>>   else
>> [place_or_version, { require: false }]
>>   end
>> end
>>
>> ruby_version_segments = Gem::Version.new(RUBY_VERSION.dup).segments
>> minor_version = ruby_version_segments[0..1].join('.')
>>
>> group :development do
>>   gem "fast_gettext", '1.1.0', require: false if
>> Gem::Version.new(RUBY_VERSION.dup) < Gem::Version.new('2.1.0')
>>   gem "fast_gettext",  require: false if
>> Gem::Version.new(RUBY_VERSION.dup) >= Gem::Version.new('2.1.0')
>>   gem "json_pure", '<= 2.0.1', require: false if
>> Gem::Version.new(RUBY_VERSION.dup) < Gem::Version.new('2.0.0')
>>   gem "json", '= 1.8.1',   require: false if
>> Gem::Version.new(RUBY_VERSION.dup) == Gem::Version.new('2.1.9')
>>   gem "json", '<= 2.0.4',  require: false if
>> Gem::Version.new(RUBY_VERSION.dup) == Gem::Version.new('2.4.4')
>>   gem "puppet-module-posix-default-r#{minor_version}", require: false,
>> platforms: [:ruby]
>>   gem "puppet-module-posix-dev-r#{minor_version}", require: false,
>> platforms: [:ruby]
>>   gem "puppet-module-win-default-r#{minor_version}",   require: false,
>> platforms: [:mswin, :mingw, :x64_mingw]
>>   gem "puppet-module-win-dev-r#{minor_version}",   require: false,
>> platforms: [:mswin, :mingw, :x64_mingw]
>> end
>>
>> puppet_version = ENV['PUPPET_GEM_VERSION']
>> facter_version = ENV['FACTER_GEM_VERSION']
>> hiera_version = ENV['3.5.0']
>>
>>
>> gems = {}
>>
>> gems['puppet'] = location_for(puppet_version)
>>
>> # If facter or hiera versions have been specified via the environment
>> # variables
>>
>> gems['facter'] = location_for(facter_version) if facter_version
>> gems['hiera'] = location_for('3.5.1') if hiera_version
>>
>> if Gem.win_platform? && puppet_version =~ %r{^(file:///|git://)}
>>   # If we're using a Puppet gem on Windows which handles its own
>> win32-xxx gem
>>   # dependencies (>= 3.5.0), set the maximum versions (see PUP-6445).
>>   gems['win32-dir'] =  ['<= 0.4.9', require: false]
>>   gems['win32-eventlog'] = ['<= 0.6.5', require: false]
>>   gems['win32-process'] =  ['<= 0.7.5', require: false]
>>   gems['win32-security'] = ['<= 0.2.5', require: false]
>>   gems['win32-service'] =  ['0.8.8', require: false]
>> end
>>
>> gems.each do |gem_name, gem_params|
>>   gem gem_name, *gem_params
>> end
>>
>> # Evaluate Gemfile.local and ~/.gemfile if they exist
>> extra_gemfiles = [
>>   "#{__FILE__}.local",
>>   File.join(Dir.home, '.gemfile'),
>> ]
>>
>> extra_gemfiles.each do |gemfile|
>>   if File.file?(gemfile) && File.readable?(gemfile)
>> eval(File.read(gemfile), binding)
>>   end
>> end
>

Re: [Puppet Users] PDK on bionic Ubuntu

[Peter Berghold]

Gemfile
source ENV['GEM_SOURCE'] || 'https://rubygems.org'

def location_for(place_or_version, fake_version = nil)
  git_url_regex = %r{\A(?(https?|git)[:@][^#]*)(#(?.*))?}
  file_url_regex = %r{\Afile:\/\/(?.*)}

  if place_or_version && (git_url = place_or_version.match(git_url_regex))
[fake_version, { git: git_url[:url], branch: git_url[:branch], require:
false }].compact
  elsif place_or_version && (file_url =
place_or_version.match(file_url_regex))
['>= 0', { path: File.expand_path(file_url[:path]), require: false }]
  else
[place_or_version, { require: false }]
  end
end

ruby_version_segments = Gem::Version.new(RUBY_VERSION.dup).segments
minor_version = ruby_version_segments[0..1].join('.')

group :development do
  gem "fast_gettext", '1.1.0', require: false if
Gem::Version.new(RUBY_VERSION.dup) < Gem::Version.new('2.1.0')
  gem "fast_gettext",  require: false if
Gem::Version.new(RUBY_VERSION.dup) >= Gem::Version.new('2.1.0')
  gem "json_pure", '<= 2.0.1', require: false if
Gem::Version.new(RUBY_VERSION.dup) < Gem::Version.new('2.0.0')
  gem "json", '= 1.8.1',   require: false if
Gem::Version.new(RUBY_VERSION.dup) == Gem::Version.new('2.1.9')
  gem "json", '<= 2.0.4',  require: false if
Gem::Version.new(RUBY_VERSION.dup) == Gem::Version.new('2.4.4')
  gem "puppet-module-posix-default-r#{minor_version}", require: false,
platforms: [:ruby]
  gem "puppet-module-posix-dev-r#{minor_version}", require: false,
platforms: [:ruby]
  gem "puppet-module-win-default-r#{minor_version}",   require: false,
platforms: [:mswin, :mingw, :x64_mingw]
  gem "puppet-module-win-dev-r#{minor_version}",   require: false,
platforms: [:mswin, :mingw, :x64_mingw]
end

puppet_version = ENV['PUPPET_GEM_VERSION']
facter_version = ENV['FACTER_GEM_VERSION']
hiera_version = ENV['3.5.0']


gems = {}

gems['puppet'] = location_for(puppet_version)

# If facter or hiera versions have been specified via the environment
# variables

gems['facter'] = location_for(facter_version) if facter_version
gems['hiera'] = location_for('3.5.1') if hiera_version

if Gem.win_platform? && puppet_version =~ %r{^(file:///|git://)}
  # If we're using a Puppet gem on Windows which handles its own win32-xxx
gem
  # dependencies (>= 3.5.0), set the maximum versions (see PUP-6445).
  gems['win32-dir'] =  ['<= 0.4.9', require: false]
  gems['win32-eventlog'] = ['<= 0.6.5', require: false]
  gems['win32-process'] =  ['<= 0.7.5', require: false]
  gems['win32-security'] = ['<= 0.2.5', require: false]
  gems['win32-service'] =  ['0.8.8', require: false]
end

gems.each do |gem_name, gem_params|
  gem gem_name, *gem_params
end

# Evaluate Gemfile.local and ~/.gemfile if they exist
extra_gemfiles = [
  "#{__FILE__}.local",
  File.join(Dir.home, '.gemfile'),
]

extra_gemfiles.each do |gemfile|
  if File.file?(gemfile) && File.readable?(gemfile)
eval(File.read(gemfile), binding)
  end
end
# vim: syntax=ruby


On Mon, Jan 28, 2019 at 10:19 AM David Schmitt 
wrote:

> please also provide the Gemfile as I've asked above. Without that it's
> impossible to reproduce locally and/or diagnose.
>
>
>
> On Mon, Jan 28, 2019 at 3:03 PM Peter Berghold 
> wrote:
>
>> Yes that was done in a module created by PDK originally.
>>
>> Here is the debug output
>>
>> peter@saltycowdawg: mediawiki]:(master): pdk test unit --debug
>> pdk (INFO): Using Ruby 2.5.1
>> pdk (INFO): Using Puppet 6.0.2
>> pdk (DEBUG): Checking for missing Gemfile dependencies.
>> pdk (DEBUG): Using '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle'
>> from PDK package.
>> pdk (DEBUG): Executing '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle
>> check --gemfile=/home/peter/prj-src/puppet/mediawiki/Gemfile --dry-run'
>> pdk (DEBUG): Command environment:
>> pdk (DEBUG):   PUPPET_GEM_VERSION: 6.0.2
>> pdk (DEBUG):   BUNDLE_IGNORE_CONFIG: 1
>> pdk (DEBUG):   GEM_HOME: /home/peter/.pdk/cache/ruby/2.5.0
>> pdk (DEBUG):   GEM_PATH:
>> /opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0
>> pdk (DEBUG):   PATH:
>> /opt/puppetlabs/pdk/private/ruby/2.5.1/bin:/home/peter/.pdk/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0/bin:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/bin:/opt/puppetlabs/pdk/bin:/home/peter/bin:/home/peter/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/opt/puppetlabs/pdk/private/git/b

Re: [Puppet Users] PDK on bionic Ubuntu

[Peter Berghold]

Yes that was done in a module created by PDK originally.

Here is the debug output

peter@saltycowdawg: mediawiki]:(master): pdk test unit --debug
pdk (INFO): Using Ruby 2.5.1
pdk (INFO): Using Puppet 6.0.2
pdk (DEBUG): Checking for missing Gemfile dependencies.
pdk (DEBUG): Using '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle' from
PDK package.
pdk (DEBUG): Executing '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle
check --gemfile=/home/peter/prj-src/puppet/mediawiki/Gemfile --dry-run'
pdk (DEBUG): Command environment:
pdk (DEBUG):   PUPPET_GEM_VERSION: 6.0.2
pdk (DEBUG):   BUNDLE_IGNORE_CONFIG: 1
pdk (DEBUG):   GEM_HOME: /home/peter/.pdk/cache/ruby/2.5.0
pdk (DEBUG):   GEM_PATH:
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0
pdk (DEBUG):   PATH:
/opt/puppetlabs/pdk/private/ruby/2.5.1/bin:/home/peter/.pdk/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0/bin:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/bin:/opt/puppetlabs/pdk/bin:/home/peter/bin:/home/peter/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/opt/puppetlabs/pdk/private/git/bin
pdk (DEBUG): Execution of
'/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle check
--gemfile=/home/peter/prj-src/puppet/mediawiki/Gemfile --dry-run' complete
(duration: 2.847360904s; exit code: 0)
pdk (DEBUG): Updating Gemfile dependencies.
pdk (DEBUG): Using '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle' from
PDK package.
pdk (DEBUG): Executing '/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle
lock --lockfile=/home/peter/prj-src/puppet/mediawiki/Gemfile.lock --update
--local'
pdk (DEBUG): Command environment:
pdk (DEBUG):   BUNDLE_GEMFILE: /home/peter/prj-src/puppet/mediawiki/Gemfile
pdk (DEBUG):   PUPPET_GEM_VERSION: 6.0.2
pdk (DEBUG):   BUNDLE_IGNORE_CONFIG: 1
pdk (DEBUG):   GEM_HOME: /home/peter/.pdk/cache/ruby/2.5.0
pdk (DEBUG):   GEM_PATH:
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0
pdk (DEBUG):   PATH:
/opt/puppetlabs/pdk/private/ruby/2.5.1/bin:/home/peter/.pdk/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/gems/2.5.0/bin:/opt/puppetlabs/pdk/share/cache/ruby/2.5.0/bin:/opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/bin:/opt/puppetlabs/pdk/bin:/home/peter/bin:/home/peter/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/opt/puppetlabs/pdk/private/git/bin
pdk (DEBUG): Execution of
'/opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle lock
--lockfile=/home/peter/prj-src/puppet/mediawiki/Gemfile.lock --update
--local' complete (duration: 0.22216318s; exit code: 1)
pdk (FATAL):
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:289:in
`find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle
(Gem::GemNotFoundException)
from
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:308:in
`activate_bin_path'
from /opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle:23:in `'

pdk (FATAL): Unable to resolve Gemfile dependencies.
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/util/bundler.rb:185:in
`update_lock!'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/util/bundler.rb:46:in
`ensure_bundle!'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/cli/test/unit.rb:76:in
`block (2 levels) in '
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:329:in
`run_this'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:269:in
`run'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:287:in
`run'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/cri-2.10.1/lib/cri/command.rb:287:in
`run'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/lib/pdk/cli.rb:18:in
`run'
pdk (DEBUG):
/opt/puppetlabs/pdk/private/ruby/2.4.4/lib/ruby/gems/2.4.0/gems/pdk-1.8.0/exe/pdk:6:in
`'
pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/bin/pdk:23:in `load'
pdk (DEBUG): /opt/puppetlabs/pdk/private/ruby/2.4.4/bin/pdk:23:in `'


On Mon, Jan 28, 2019 at 4:27 AM David Schmitt 
wrote:

> Hi Peter,
>
> is the module compatible to the PDK? That is, have you created the module
> with the PDK, and/or ran `pdk convert`/`pdk update` successfully on it?
>
> If no, please do so before trying to run any other PDK commands in a
> module.
>
> If yes, please capture the full output of the command

[Puppet Users] PDK on bionic Ubuntu

[Peter Berghold]

When I run "pdk test unit" I get the following error:
pdk (INFO): Using Ruby 2.5.1
pdk (INFO): Using Puppet 6.0.2
pdk (FATAL):
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:289:in
`find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle
(Gem::GemNotFoundException)
from
/opt/puppetlabs/pdk/private/ruby/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems.rb:308:in
`activate_bin_path'
from /opt/puppetlabs/pdk/private/ruby/2.5.1/bin/bundle:23:in `'

pdk (FATAL): Unable to resolve Gemfile dependencies.

I did a "gem list" and bundler is installed. What is the magic foo that I
can do to make this work?


-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv1gacMoibL%3DZm9D_icP%2Bse5WvWsiSFMnp69GF2yzSra%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] grep puppet/cache/reports for failures

[Peter K]

Can anyone recommend a quick and dirty way to grep 
through puppet/cache/reports (or whatever $reportdir reports to) to find 
failures or missing reports?
I'm looking for a temporary solution before I commit to setting up 
reporting software.
thx,
-peter

-- 
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/c2503127-582d-43dc-bcda-ce6e073668fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera and precedence

[Peter Berghold]

I'm having a revertment to my noob days with respect to how hiera works.
(Version 3 for now)

If I have the hierarchy of

- common
- nodes/"%{fqdn}"
- datacenter/"%{fdatacenter}"

if in common.yaml I have "module::parms::server: server1" and in
nodes/myclient.yaml I have "module::parms::server: server2" and in
datacenter/NYCA.yaml (and the host presents NYCA as its datacenter) I have
"module::parms::server: server3" which value will be presented for host
myclient?

I could have sworn I read the lower down the list of hierarchy a value was
it would override the one above it. I just read this morning that hiera
stops at the first value it finds which is a bit of a problem for what I'm
trying to accomplish.



-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv0%2BApOXSmMJfTVOpLAH4%2Bx7uZ5dSa84mibO_%2BDr2yMD%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Concerns about Puppet 4 master serving Puppet 3 clients

[Peter Berghold]

I am about to have our first Puppet 4 Puppet master into our production
environment. We have a very large community of Puppet 3 "leaf nodes" being
managed by our old Puppet 3 infrastructure.

What issues might I run into with that and what should I do to mitigate
this?

-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv0KvkdZqV6dgBNbPnoEeyKeAchrD%2Bt5wehmpwwfLGYdkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet 6 client lookup secret from Hashicorp Vault

[Peter M Souter]

Hi All!
 
I've been working on a Vagrant repo that sets everything up: 
https://github.com/petems/puppet-vault-function-vagrant

> #export VAULT_SKIP_VERIFY=true

This one you can avoid by pointing to the puppet CA cert with VAULT_CACERT, 
means you're avoiding the cert skipping.

> Our next challenge is how to isolate clients to see ONLY their own 
secrets within Vault based on the incoming name and a policy to suit (or a 
similar workflow that results in client isolation).

Yeah, this part has been difficult so far. The only way to match lookups 
based on the cert doing the lookup would be with Sentinel using 
request.data.cert matching it to the kv path. 
https://www.vaultproject.io/docs/enterprise/index.html

However, you could re-write the vault_lookup function to only allow lookups 
with the trusted cert certname in it, handling it on the Puppet side 
instead, similar to the hiera logic. I've not been able to find an example 
of doing this, but I'm looking into it.

Also, you can restrict the policy on the Vault side based on Certificate 
attributes, so you could have a more general policy based on OIDs etc:

 vault write auth/cert/certs/puppetserver \

display_name=puppet \
policies=all_secrets \
certificate=@/etc/vault/keys/ca_cert.pem \
required_extensions="1.3.6.1.4.1.34380.1.1.22:vaultok" \
ttl=3600



  cat << EOF > /etc/puppetlabs/puppet/csr_attributes.yaml
---
extension_requests:
  pp_securitypolicy: "vaultok"
EOF


On Friday, 11 January 2019 04:46:58 UTC, comport3 wrote:
>
> We now have Vault lookups working using the Deferred functionality that 
> debuted in Puppet6x.
>
> Here are my high level note on "how", hoping they help someone else in the 
> future (lots of assumptions, but if you have questions please reach out...)
>
> #export VAULT_SKIP_VERIFY=true
> #mkdir /var/lib/vault
> #chown puppet:puppet /var/lib/vault
> #vault operator init -key-shares=1 -key-threshold=1
> # (securely record keys and tokens)
> #export VAULT_TOKEN=TheTokenFromAbove
> #vault operator unseal
> # (unseal key from above)
> #vault auth enable cert
> #vault write auth/cert/certs/puppetserver display_name=puppet 
> policies=prod,test certificate=@/etc/puppetlabs/puppet/ssl/ca/ca_crt.pem 
> ttl=3600
> #vault kv put secret/test hello=world
> #echo "path \"secret/test\" {capabilities = [\"read\",\"list\"]}" > 
> test.hcl
> #vault policy write test test.hcl
> #  (enable vault profile::vaulttest in Hiera & deploy, test Puppet and see 
> the KV output)
>
> Our next challenge is how to isolate clients to see ONLY their own secrets 
> within Vault based on the incoming name and a policy to suit (or a similar 
> workflow that results in client isolation).
>
> If any Vault users has any advice it would be welcome.
>
> On Monday, November 5, 2018 at 4:56:36 PM UTC+11, comport3 wrote:
>>
>> Hi Lindsay and Thomas,
>>
>> Thanks for your documentation - I'm having some problems getting the 
>> client lookup to work.
>>
>> I have the Puppetserver CA setup in Vault, and the Vault servers Puppet 
>> certificate and private key configured.
>>
>> I have added the Puppetserver CA to the trusted roots, per: 
>> https://github.com/hashicorp/vault/issues/438
>>
>> I have configured Vault ('auth enable cert', 'vault write 
>> auth/cert/certs/puppetserver...') successfully (or so it seems) and Vault 
>> is unlocked.
>>
>> Now I can get a test lookup to work using this CURL command -
>> curl -X GET -H "X-Vault-Token:$VAULT_TOKEN" 
>> https://vault1.domain.com:8200/v1/secret/test
>>
>> But configuring via Puppet code, I get -
>> Error: Failed to apply catalog: Received 403 response code from vault at 
>> vault1.domain.com for secret lookup (api errors: ["1 error 
>> occurred:\n\t* permission denied\n\n"])
>>
>> Any ideas what I'm missing?
>>
>> On Saturday, October 13, 2018 at 2:20:02 AM UTC+11, Lindsey Smith wrote:
>>>
>>>
>>>
>>> On Wed, Oct 10, 2018 at 5:28 AM Thomas Müller  
>>> wrote:
>>>


 Am Dienstag, 9. Oktober 2018 14:12:39 UTC+2 schrieb comport3:
>
> Mentioned in the Puppet 6 release notes are the ability for a client 
> to lookup secret data from Vault.
>
> Is there any more info on how to implement this?
>
> I have done extensive work on POC environments that use Vault as a top 
> level in Hierarchy and mark the secrets as 'sensitive' so they do not 
> appear in logs and reports, but do not want to continue deploying this 
> methodology if it's not the way the technology is headed.
>
> https://github.com/comport3/puppet5-hiera-vault-poc
>

 from https://puppet.com/docs/puppet/6.0/using_a_deferred_function.html  
 :

 The Forge already hosts some community modules that provide 
> integrations with secret store, like the following:
>
>- 
>
>Azure Key Vault: works on both the master and the server
>- 
>
>Cyberark Conjur: works on the master 
>- 
>
>   

Re: [Puppet Users] Re: Puppet 3 and hiera

[Peter Berghold]

>> Is there any chance that you have *too new* an Hiera installed?

I was actually worried at first that there was a regression in terms of
what hiera was on there given the host was "patched" recently.  I may have
found the problem and yes I suspected right along the issue was on the
remote master not the client.  (well except for a brief moment in time at
around 6AM the installation starting at midnight... I was a bit foggy then.)

I'm deploying a "fix" and if it works I'm going to post as much here.



On Thu, Jan 10, 2019 at 9:57 AM jcbollinger 
wrote:

>
>
> On Wednesday, January 9, 2019 at 11:06:54 AM UTC-6, Salty Old Cowdawg
> wrote:
>>
>> Hi folks,
>>
>> I know... I know... get off of Puppet 3.  I'll be getting there soon.
>>
>> Right now I have Puppet 3 in our production environment where I work.
>> Long political story as to why we are still on 3 that I won't get into.   I
>> just did a release of the Puppet code and one of the "features" of the
>> release is moving all the data out of the code into hiera.
>>
>> This has been shaken out and tested thoroughly and works fine. So far so
>> good.  Superficially at least both the production and lab environments
>> match each other in terms of Puppet version OS etc.   Both lab and
>> production use RHEL 6.5 (?) and here's where the issue comes in.
>>
>> Puppet servers (I have a tiered environment, grand master -> manages ->
>> remote masters -> manage clients) all seem to be working fine.  On the
>> client nodes the Puppet agent terminates with an error:
>>
>> Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error
>> +RuntimeError: Hiera terminus not supported without hiera library at
>> +/etc/puppet/environments/Production/manifests/site.pp:24 on node
>> +
>>
>>
>
> This may already be clear to you, but just in case, do note that although
> this error is *reported* on the clients, it *occurs* on their master.  I
> guess that's one or more of the remote masters.  If you're thinking in
> terms of what is installed on the agent machines then that could be
> throwing you off.  Does the Hiera command-line tool run on the relevant
> masters?
>
> I'm afraid I don't know where to find P3 docs any longer, but if I did, I
> would be looking for clues among the installation instructions.  The docs
> now available for both Puppet overall and for the Hiera subsystem both
> assume that you'll get Hiera in the same package that provides Puppet, or
> at least as a dependency of that package.
>
>
>
>> I did some Googling looking for a solution and I found one mention of the
>> need for a "ruby-hiera" package.  This is not installed in our test lab so
>> this seems to be a red herring to me but I'm very willing to be wrong.
>>
>
>
> Hmm.  I don't find a "ruby-hiera" in Fedora's Koji system.  Their Hiera
> packages (i.e. those that go into EPEL) are named simply "hiera".  And
> their Puppet packages, including for Puppet 3, have that "hiera" package as
> a dependency.
>
>
> The line of code the error is happening on cited above is simple
>> hiera_include('classes');
>>
>> Thoughts anybody?
>>
>
>
> Is there any chance that you have *too new* an Hiera installed?
>
>
> 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/d4efba93-eadd-4171-8493-e25500e7dcc8%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/d4efba93-eadd-4171-8493-e25500e7dcc8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv3PY8BPHcoHzMOHG3eeuxGg-fSkhTw-cq8Ji7s-JD%3Dh-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 3 and hiera

[Peter Berghold]

Hi folks,

I know... I know... get off of Puppet 3.  I'll be getting there soon.

Right now I have Puppet 3 in our production environment where I work.  Long
political story as to why we are still on 3 that I won't get into.   I just
did a release of the Puppet code and one of the "features" of the release
is moving all the data out of the code into hiera.

This has been shaken out and tested thoroughly and works fine. So far so
good.  Superficially at least both the production and lab environments
match each other in terms of Puppet version OS etc.   Both lab and
production use RHEL 6.5 (?) and here's where the issue comes in.

Puppet servers (I have a tiered environment, grand master -> manages ->
remote masters -> manage clients) all seem to be working fine.  On the
client nodes the Puppet agent terminates with an error:

Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error
+RuntimeError: Hiera terminus not supported without hiera library at
+/etc/puppet/environments/Production/manifests/site.pp:24 on node
+

I did some Googling looking for a solution and I found one mention of the
need for a "ruby-hiera" package.  This is not installed in our test lab so
this seems to be a red herring to me but I'm very willing to be wrong.

The line of code the error is happening on cited above is simple
hiera_include('classes');

Thoughts anybody?
-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv281q9BHN5eY22MCcS_rtQ4utkmfYffY15b0cRtuUCg_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] A GUI tool for Hiera

[Peter Berghold]

I don't want to sound harsh but I'm going to be blunt.   I could not get
this thing to work for me on Linux (Ubuntu) even when doing an "npm audit
fix" followed by an "npm audit fix --force" followed by an "npm install"

Very disappointing to me.

On Tue, Jan 8, 2019 at 12:57 PM desertkun  wrote:

> Hello, everyone.
>
> I have made a small useful open source project for Puppet/Hiera, so I hope
> you can excuse me a bit of advertisement of it for greater good.
>
> https://github.com/desertkun/hiera-editor
>
> Basically it takes editing Hiera configurations to a new level.
> It parses modules with puppet-strings to extract class information like
> field names, types and doc strings, and retrieves default values of class
> fields
> by doing best-effort compilation (with puppet-parser) of Puppet AST on
> your machine. So no more typos and less of "commit-deploy-check" cycles.
>
>
>
> The goal of the project is to help manage servers with Puppet to those who
> far away from the back-end, including Puppet itself,
> like "I need to deploy nglinx but I have installed debian for the first
> time". So if you have a project that complex that requires Puppet to deploy
> it, having some
> tool to introduce Puppet to end users of your project might improve the
> learning curve.
>
> Would really appreciate any input on the idea, including concerns like
> "there's no need for this" as I just have made the project public and still
> not sure if I should continue.
>
> Regards.
>
> --
> 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/1eb43a86-8f65-42d6-910f-9d45a8789256%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/1eb43a86-8f65-42d6-910f-9d45a8789256%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Peter L. Berghold   salty.cowd...@gmail.com

h <http://blog.berghold.net>ttp://science-fiction.berghold.net

-- 
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/CAArvnv3GL%3Dy4hrxn90OBHB-eKgzep8LtvJM31PucJn1ff%3DprcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

REGRESSION - Re: [Puppet Users] Announcement: Release of Puppet Platform 6.0.1

[Peter Meier]

Hi All,

> We're happy to announce the release of Puppet Platform 6.0.1. This is
> primarily a bug release, with some improvements to Puppet, some new
> features in Puppet Server, and some new component versions in Puppet
> Agent.

Just a heads up to everybody: There is a pretty severe regression in the
exec provider together with cwd, as the behavior of the type/provider
changed from 6.0.0 to 6.0.1:

https://tickets.puppetlabs.com/browse/PUP-9194

tldr; The cwd param is not respected in 6.0.1 for the commands specified
in unless or onlyif. This might trigger an unwanted execution of the
command, as the safe-guards in unless/onlyif might fail as they are not
anymore executed in the cwd.

best

~pete

-- 
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/9101b379-79d9-3e04-df4f-3cd0c82880bd%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Fresh install of Opensource puppetdb on RHEL 7.3 using Postgresql 9.6 pg_log errors

[Peter Krawetzky]

Just installed a new copy of postgresql 9.6 on a server that was running 
9.4.  Upgraded puppetdb to 5.2.4 on the same server.

After startup the pg_log file has been throwing the following error:
ERROR:  canceling autovacuum task

I suspect puppetdb is holding a lock but not sure where.  It also doesn't 
identify what table it's trying to autovacuum.

Anyone else experiencing this issue?  I'm worried that without autovacuum 
the database is not going to get cleaned up.

-- 
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/4c865daa-2912-4b70-8ce8-9e1fa24a5fb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] user resource on darwin throws "undefined method `each' for nil:NilClass"

[Peter K]

Martin, that was definitely the answer.
Now do you have any idea how to export that variable for the user that runs 
the puppet service...on a mac?
thx,
-peter

On Saturday, September 1, 2018 at 4:07:11 AM UTC-7, Martin Alfke wrote:
>
> Hi Peter, 
>
> please check the locale setting and set it to en_US.UTF-8 
>
> export LANG=en_US.UTF.8 
>
> Best, 
> Martin 
>
>
> > On 31. Aug 2018, at 20:48, Henrik Lindberg  > wrote: 
> > 
> > On 2018-08-31 20:23, Peter K wrote: 
> >> I'm getting this error when I try and create a user on osx: 
> >> '''Error: Failed to apply catalog: undefined method `each' for 
> nil:NilClass''' 
> >> My code looks like this: 
> >> '''  class fakeadmin2 { 
> >>   user { 'fakeadmin2': 
> >> name=> 'fakeadmin2', 
> >> ensure  => 'present', 
> >> uid   => '504', 
> >> gid   => '501', 
> >> home   => '/Users/fakeadmin2', 
> >>   } 
> >> }''' 
> >> ubuntu server package: puppetserver2.8.0-1puppetlabs1 
> >> puppet master 4.10.9 
> >> puppet agent version 4.10.9 
> >> Any help with how to debug this would be helpful too. 
> > 
> > A stack trace is required to have any guess at what is going wrong. (Run 
> puppet apply with --trace) 
> > 
> > Also check here (https://puppet.com/docs/puppet/4.10/release_notes.html) 
> for release notes for versions newer that 4.10.9 (think we are up to 12 
> now). 
> > 
> > 
> > - henrik 
> > 
> >> thx 
> >> -- 
> >> 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...@googlegroups.com   puppet-users+unsubscr...@googlegroups.com >. 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/7114fc76-ba6e-4ecf-a4b9-efe12f5c297b%40googlegroups.com
> <
> https://groups.google.com/d/msgid/puppet-users/7114fc76-ba6e-4ecf-a4b9-efe12f5c297b%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > 
> > Visit my Blog "Puppet on the Edge" 
> > http://puppet-on-the-edge.blogspot.se/ 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/pmc2e2%24tdg%241%40blaine.gmane.org.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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/68a68332-1f6e-4d16-9f33-32ef3216b0f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] user resource on darwin throws "undefined method `each' for nil:NilClass"

[Peter K]

Thank you Henrik. That was useful. I"ll keep that in my bag of tricks.
-peter

On Friday, August 31, 2018 at 11:48:52 AM UTC-7, Henrik Lindberg wrote:
>
> On 2018-08-31 20:23, Peter K wrote: 
> > I'm getting this error when I try and create a user on osx: 
> > '''Error: Failed to apply catalog: undefined method `each' for 
> > nil:NilClass''' 
> > 
> > My code looks like this: 
> > 
> > '''  class fakeadmin2 { 
> >user { 'fakeadmin2': 
> >  name=> 'fakeadmin2', 
> >  ensure  => 'present', 
> >  uid   => '504', 
> >  gid   => '501', 
> >  home   => '/Users/fakeadmin2', 
> >} 
> > }''' 
> > 
> > ubuntu server package: puppetserver2.8.0-1puppetlabs1 
> > 
> > puppet master 4.10.9 
> > puppet agent version 4.10.9 
> > 
> > 
> > Any help with how to debug this would be helpful too. 
>
> A stack trace is required to have any guess at what is going wrong. (Run 
> puppet apply with --trace) 
>
> Also check here (https://puppet.com/docs/puppet/4.10/release_notes.html) 
> for release notes for versions newer that 4.10.9 (think we are up to 12 
> now). 
>
>
> - henrik 
>
> > thx 
> > 
> > -- 
> > 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...@googlegroups.com  
> > <mailto:puppet-users+unsubscr...@googlegroups.com >. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/7114fc76-ba6e-4ecf-a4b9-efe12f5c297b%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/puppet-users/7114fc76-ba6e-4ecf-a4b9-efe12f5c297b%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>
> -- 
>
> Visit my Blog "Puppet on the Edge" 
> http://puppet-on-the-edge.blogspot.se/ 
>
>

-- 
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/c145bf94-a448-4476-ae99-41c5a70e2e60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: user resource on darwin throws "undefined method `each' for nil:NilClass"

[Peter K]

The puppet agent is on a mac with 10.13.4.

On Friday, August 31, 2018 at 2:23:03 PM UTC-4, Peter K wrote:
>
> I'm getting this error when I try and create a user on osx:
> '''Error: Failed to apply catalog: undefined method `each' for 
> nil:NilClass'''
>
> My code looks like this:
>
> '''  class fakeadmin2 {
>   user { 'fakeadmin2':
> name=> 'fakeadmin2',
> ensure  => 'present',
> uid   => '504',
> gid   => '501',
> home   => '/Users/fakeadmin2',
>   }
> }'''
>
> ubuntu server package: puppetserver2.8.0-1puppetlabs1
>
> puppet master 4.10.9
> puppet agent version 4.10.9
>
>
> Any help with how to debug this would be helpful too.
> thx
>

-- 
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/0538c881-00cc-46a8-bae9-5155a72c035e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] user resource on darwin throws "undefined method `each' for nil:NilClass"

[Peter K]

I'm getting this error when I try and create a user on osx:
'''Error: Failed to apply catalog: undefined method `each' for 
nil:NilClass'''

My code looks like this:

'''  class fakeadmin2 {
  user { 'fakeadmin2':
name=> 'fakeadmin2',
ensure  => 'present',
uid   => '504',
gid   => '501',
home   => '/Users/fakeadmin2',
  }
}'''

ubuntu server package: puppetserver2.8.0-1puppetlabs1

puppet master 4.10.9
puppet agent version 4.10.9


Any help with how to debug this would be helpful too.
thx

-- 
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/7114fc76-ba6e-4ecf-a4b9-efe12f5c297b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet Platform 5.5.6 is now available!

[Peter Meier]

Hi

thanks for the answer.

> We hope to have another release relatively soon that allows you update
> the settings (and resolve the deprecation warnings).

Yeah would make sense to have that rather sooner than later. While I
understand why you want to get deprecation warnings in as early as
possible, there must be an alternative to migrate to (if the feature is
not to be dropped at all).

With deprecation warnings you want to signalize folks that they have to
act and adjust their configuration. But at the moment they just can't do
anything other than ignoring it, which defeats the whole purpose of that
warning. And eventually will make them also ignoring other warnings.

best pete

-- 
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/a92cd9d0-e215-71bc-c554-fe108d9ae34d%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Announce: Puppet Platform 5.5.6 is now available!

[Peter Meier]

On 08/22/2018 08:42 PM, Molly Waggett wrote:
> Puppet Platform 5.5.6 is a bug-fix, feature, and deprecations release
> that includes updates for Puppet 5.5.6, Facter 3.11.4, and Puppet agent
> 5.5.6. For details, see the Puppet
> , Facter
> ,
> and puppet-agent 
> release notes.

So this release deprecates autosign:

Warning: Setting autosign is deprecated.
   (location:
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in
`issue_deprecation_warning')

But to what should this configuration option now be migrated so there is
no deprecation warning anymore?

>From what I see when scanning through docs and jira, the new options are
not yet implemented. So we just have to live with the deprecation
warnings? Or what am I missing?

best

~pete

-- 
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/6872e14d-6379-f592-f68f-d4d2bc031642%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] More oddities with installting FOSS version of Puppet

[Peter Berghold]

Josh,

I wiped the entire trees meaning /opt/puppetlabs and /etc/puppetlabs
recursive.

On Wed, Jul 25, 2018, 16:17 Josh Cooper  wrote:

> On Wed, Jul 25, 2018 at 6:16 AM Peter Berghold 
> wrote:
> >
> > Once again I undertook trying to get a puppetserver in my personal
> computing environment to work and during a fresh install of puppetserver
> (removing agent and server first) and clearing the /opt/puppetlabs and
> /etc/puppetlabs directories I see the following complaints:
>
> Did you delete the /opt/puppetlabs and /etc/puppetlabs directories or
> delete their contents? If it's the latter, it may be that the
> puppet-agent package doesn't recreate the intermediate directories,
> e.g. /opt/puppetlabs/puppet/share, causing later steps to fail.
>
> >
> > Setting up puppet-agent (1.10.14-1xenial) ...
> > chmod: cannot access
> '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftdetect/puppet.vim': No
> such file or directory
> > chmod: cannot access
> '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftplugin/puppet.vim': No
> such file or directory
> > chmod: cannot access
> '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/indent/puppet.vim': No
> such file or directory
> > chmod: cannot access
> '/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/syntax/puppet.vim': No
> such file or directory
> > chmod: cannot access
> '/etc/puppetlabs/code/environments/production/environment.conf': No such
> file or directory
> > Setting up puppetserver (2.8.1-1puppetlabs1) ...
> > usermod: no changes
> >
> > This is on an Ubuntu 16 server and still puppetserver complains about
> stuff being missing such as the CAservice now.
> >
> > Anybody else run into this?
> >
> >
> > --
> > 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/CAArvnv2UyOurHTWArzv7DWUtjtJb85C%2BAPZb%3D2EQAYfF%2B-HScw%40mail.gmail.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> Josh
>
> --
> Josh Cooper | Software Engineer
> j...@puppet.com | @coopjn
>
> --
> 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/CA%2Bu97unXLyfrqDJ4n72%2BvR6SYjja%2B9EvFzhWA%3D5MRbMv_VWPFg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAArvnv2zAT7pnhPc8WC70x-QskMAOyUqdmQtbhMZDHx8YxSxZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Amplification of the issues I'm encountering with puppetserver on Ubuntu 16

[Peter Berghold]

It would appear that at least a majority of the configuration files that
puppetserver needs to start up do not exist.  Is this by design?

-- 
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/CAArvnv2UzobkZze6PwwTLFWhF7a5PxF0hgR3nihzXQotW_R6Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] More oddities with installting FOSS version of Puppet

[Peter Berghold]

Once again I undertook trying to get a puppetserver in my personal
computing environment to work and during a fresh install of puppetserver
(removing agent and server first) and clearing the /opt/puppetlabs and
/etc/puppetlabs directories I see the following complaints:

Setting up puppet-agent (1.10.14-1xenial) ...
chmod: cannot access
'/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftdetect/puppet.vim': No
such file or directory
chmod: cannot access
'/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/ftplugin/puppet.vim': No
such file or directory
chmod: cannot access
'/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/indent/puppet.vim': No
such file or directory
chmod: cannot access
'/opt/puppetlabs/puppet/share/vim/puppet-vimfiles/syntax/puppet.vim': No
such file or directory
chmod: cannot access
'/etc/puppetlabs/code/environments/production/environment.conf': No such
file or directory
Setting up puppetserver (2.8.1-1puppetlabs1) ...
usermod: no changes

This is on an Ubuntu 16 server and still puppetserver complains about stuff
being missing such as the CAservice now.

Anybody else run into this?

-- 
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/CAArvnv2UyOurHTWArzv7DWUtjtJb85C%2BAPZb%3D2EQAYfF%2B-HScw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] woes installing Puppet server (won't start)

[Peter Berghold]

I've been running my own personal Puppet server at home for a very long
time and have rebuilt and installed Puppet server many times so what is
going on now makes no sense to me.

Yesterday I decided to rebuild my Puppet master yet again and loaded the
puppetserver package from:

puppetlabs-release-pc1-xenial.deb
puppet5-release-xenial.deb
puppet5-release-stretch.deb
puppet5-nightly-release-stretch.deb

In that order.

I'm running on Ubuntu (14?) and in none of the above versions does the
puppetserver process start up and stay up.  Gleaning the journal
(journalctl -u puppetserver --follow) I find this little nugget of fun:
Jul 20 06:13:03 myserver.tld  puppetserver[24046]: 06:13:03.762 [main]
ERROR puppetlabs.trapperkeeper.internal - Error during app buildup!
Jul 20 06:13:03 mysever.tld puppetserver[24046]:
java.lang.RuntimeException: Service ':FilesystemWatchService' not found

What the heck is that about?  What do I need to do to fix this?

Thanks in advance.

-- 
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/CAArvnv0PKo0%3DVV2xBTZ2doF%3Dz1Kqb9e-%3D03oDd57%3DcdV107gag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Style (syntax?) question

[Peter Berghold]

I was looking at someone else's code one day last week and saw a pattern
I've not seen before. Maybe that's what I get for developing Puppet code in
a vacuum. :-)

class someclass (
$parm1 = $::someclass::params::parm1,
$parm2 = $::someclass::params::parm2   # so far I get it.
) inherits someclass::params { # ok, I get it

 class{'someclass::package': }# OK
 -> class('someclass::configure':}# right...
 -> Class{'someclass':}#  HUH?  What does that do?
}

Is that last step necessary and why?

-- 
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/CAArvnv22e-Wbp8dtD9bUHTOxf68e8p3rWdNP8A2pFR6txAamzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet hiera variable

[Peter Bukowinski]

Jagga,

It’s a simple error. You need to remove the square brackets from around your 
conditional test. Puppet is evaluating it as an array, and since puppet treats 
all non-boolean values (other than undef) as true, you will never get to the 
else block.

—
Peter

> On Apr 3, 2018, at 10:13 PM, Jagga Soorma <jagg...@gmail.com> wrote:
> 
> Hi Guys,
> 
> I am using foreman and puppet to provision/manage systems.  I have a simple 
> motd module that I was using for all my systems but now have a need to setup 
> a different motd for a specific hostgroup/type of systems.  So, I though I 
> would use the hostgroup hiera setup from foreman/puppet to decide which motd 
> to use.  I wrote something quickly to test but have unexpected results and 
> was hoping someone here can help me make sense of this:
> 
> --
> my hostgroup for system 1 is CSOE73_Prod/hpc/misc and for system 2 is 
> CSOE73_Prod/hpc/compute.  So I decided to write the code this way:
> 
> if [$hostgroup == 'CSOE73_Prod/hpc/misc'] {
>   file { "/etc/motd":
> ensure => file,
> content => template('clientos/motd.erb')
>  }
> } 
> else {
>   file { "/etc/motd":
> ensure => file,
> source => 'puppet:///modules/clientos/etc/motd 
> ',
> mode => 644,
> owner => 'root',
> group => 'root',
> }
> }
> --
> 
> However, for both systems the motd.erb template is being applied.  However, 
> my expectation was that for system 2 it would just use the files/etc/motd 
> file.  Is it maybe the backslash in CSOE73_Prod/hpc/misc that might be 
> throwing it off?  Am I going about this totally the wrong way?  
> 
> Any help would be greatly appreciated!
> 
> Thanks,
> -J

-- 
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/2019AE2E-05AC-4964-AC10-AD3A712ADD49%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: containment questions

[Peter Bauer]

Am Freitag, 16. Februar 2018 04:09:34 UTC+1 schrieb Jeremiah Powell:
>
> You can also use stages to define strong barriers to order large parts of 
> a task.  The canonical example is configuring a database before the 
> application that needs it.
>

But stages are not transitive either so the stage has to be given for every 
subclass like with the contain function.
 

>
> Using contain on a defined type is not a syntax error.  But you won't 
> provide any of the parameters on the defined type when you use contain.  
> This includes parameter like a unique name.  So the semantic meaning is 
> rather curious. It adds a tag to the define type with the name of the class 
> then adds a dependency between instances of the defined type and the 
> class.  All of the defined type instances. That won't help you, though, for 
> two reasons.  First, depending on the version of Puppet the resources in 
> the defined type won't get the relationship.
>

So the bottom-line is that for defined types the new contain function is 
useless and we need to stick to the anchor pattern. Sounds like an 
incomplete feature to me.
 

>
> Look at the graph for your node.
>
> You should see the resources in your sub-classes 'floating' off the 
> graph.  They should have no relationship to anything else.   
>
> Secondly, this will still have the same sub-class issue. You can see this 
> here:
>
>
> https://ask.puppet.com/question/18868/containment-with-role-and-profile-pattern/
>
>
thx for the link, good read. The light-weight version of the anchor pattern 
shown by Piennar should cover most cases and looks better than the anchors 
everywhere.
 

> Sub-sub-classes in Puppet are not tagged with their ancestor (parent and 
> parent's parent, etc) tags.  
>

Though i guess it would be possible to implement a transitive version of 
the contain function. This would make it easier for module writers and also 
for the users since it is clearly visible in the main class that everything 
happens in there and no resources are floating around.
 

>
> Setting containment manually adds all the tags for the current class 
> explicitly.  It also adds the relationship in the catalog between those 
> tags.
>
> In the link above: role class -> profile class -> utility class -> 
> resource.  The resource is tagged with the utility class's name but not the 
> profile or role name.  So you could not create relationships at the 
> meta-level of roles or profiles.
>
> Requires is another way to do this.
>
> https://puppet.com/docs/puppet/5.4/lang_classes.html#using-include
>
> The function create_resources() was a great way to trigger this behavior 
> for a long time. Resources generated by this function did not have tags 
> from the class in which create_resources was run.  Using create_resources 
> to get  'fake looping' means explicit resource dependencies were required.  
>
> This is one reason to replace create_resources with using the hash (* =>) 
> attribute and lambdas.
>
>
> https://puppet.com/docs/puppet/4.9/lang_resources_advanced.html#implementing-the-createresources-function
>
> I still order things explicitly at the resource level.   Abstractions like 
> classes and defines are nice programmer candy.  The Puppet agent only cares 
> about the resources in the catalog. If  I'm having to add contains 
> everywhere that tells me my fancy class structure is not adding value.  It 
> is just adding more work for me.
>
> In the end it is about making a server do something correct.  Do I want a 
> service to start after another service? I include the dependency between 
> the service resources directly.  The result is that I have much smaller 
> modules with obvious behavior.
>
> On Thursday, February 15, 2018 at 2:02:41 AM UTC+8, Peter Bauer wrote:
>>
>> hi,
>>
>> i was recently bitten by ordering issues caused by missing contain/anchor 
>> declarations in a PostgreSQL module which should have finished its job 
>> before configuring and starting the PuppetDB which is done by another 
>> module.
>> So here are my questions:
>> - is it possible to use the contain function also for defined resource 
>> types/defines? I ended up using anchors since i could not find out how to 
>> use contain here.
>> - am i the only one thinking that it is too error-prone and cumbersome to 
>> add a contain everytime a sub-class is instantiated in a module? Since it 
>> is not transitive it has to be added on every abstraction layer of a 
>> module, from the init.pp down to all sub-classes until there are just 
>> classes left declaring resources directly. And in case one contain is 
>> missing, that code may be executed in the wrong time.
>>
>> t

[Puppet Users] containment questions

[Peter Bauer]

hi,

i was recently bitten by ordering issues caused by missing contain/anchor 
declarations in a PostgreSQL module which should have finished its job before 
configuring and starting the PuppetDB which is done by another module.
So here are my questions:
- is it possible to use the contain function also for defined resource 
types/defines? I ended up using anchors since i could not find out how to use 
contain here.
- am i the only one thinking that it is too error-prone and cumbersome to add a 
contain everytime a sub-class is instantiated in a module? Since it is not 
transitive it has to be added on every abstraction layer of a module, from the 
init.pp down to all sub-classes until there are just classes left declaring 
resources directly. And in case one contain is missing, that code may be 
executed in the wrong time.

thx,
Peter

-- 
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/ee5e4a5d-99e7-4c18-a30a-1ccd316233da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] does puppetdb 4.x handle brief postgresql backend outage

[Peter Bauer]

I have an older version, however PuppetDB reconnects on the first Agent run so 
the first one fails but subsequent runs will succeed.

-- 
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/e9f166c4-98ce-4684-a4d6-8d09c67443cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Announce: Puppet Platform 5.3.4 is now available

[Peter Meier]

> The puppet agent indeed has a default config  that I did not specify –
> and don’t want to, I’m running with a puppetserver :
>
> # puppet config print environmentpath
>
> /etc/puppetlabs/code/environments
>
> # grep env /etc/puppetlabs/puppet/puppet.conf
>
> environment = dev
>
> ð  Question : what am I doing wrong ?

I realized this morning (after the update) that updating the RPM (and
likely also the deps) overwrite/enforce various settings:

https://tickets.puppetlabs.com/browse/CPR-515

Maybe you are affected by the same bug?

As I read from your email, you get a warning that puppetserver can't
find things in

/etc/puppetlabs/code/environments

Is this, where your code should live? Are your environments there?

If not, then maybe changing it back to what you had there helps?

To me it looks like puppetserver isn't searching in /puppet/code/envs
but rather /etc/puppetlabs/code/environments

best

~pete

-- 
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/5c56964f-8eea-2e35-03d1-14636274fb6e%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: Customizing existing types / providers

[Peter Faller]

Are the errata available as YUM packages? In that case it might be simpler 
to create a separate repository (using createrepo) and a Puppet yumrepo 
resource.

On Friday, 2 February 2018 18:05:26 UTC+2, Andrew Schofield wrote:
>
> Hi all,
>
> I'm trying to customize the existing package type by adding an additional 
> option for the ensure option so that I would be able to do the following:
>
> package { 'RHSA-2018:0001' : 
>   ensure => 'errata'
> }
>
> I have a new provider named errata which sort of works but is far too 
> sensitive to other options (as I can't find out how to customize the type) 
> I'd rather not specify a new provider unless there is no other way. The 
> idea behind this is to extend the default Package resource type to include 
> support for errata on Fedora / RHEL systems. 
>
> Does anybody have any hints and/or links to documentation which might 
> explain how (or even if) this is achievable? My googling isn't really 
> bringing much useful information. 
> Thanks,
> Andrew
>

-- 
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/e4827bf8-babe-4e9e-8334-28b5aa7f0df3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] override individual items of a structured fact

[Peter Bauer]

hi,

since the stock 'networking' fact does not find the correct "primary" 
network interface in my case (there is another interface with the default 
route), i want to change the related 'networking.ip', 'networking.primary' 
values of this stuctured fact by writing a custom fact in Ruby. Its 
straight-forward to replace the whole fact but how could i keep the stock 
values of the other items? As soon as i obtain the stock value of the fact 
with

stock_fact = Facter.value(:networking)

the fact is resolved and there seems to be no way of modifying it 
afterwards. Basically its a chicken-and-egg problem but if there was the 
possibility to force a re-evaluate of the fact or define resolutions just 
for single items of a fact ...

here is the complete example: 

# get the stock value of the fact
networking_fact = Facter.value(:networking)
# add a resolution for the fact but this has no impact on the final value 
of the fact since Facter does not evaluate the fact again
Facter.add(:networking, { :value => "networking" }) do
  has_weight 200
  setcode do
"does not matter what goes here"
  end
end

-- 
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/b59af634-1851-44ac-8e1d-60a0dfe45615%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PSON.load fails when string contains e.g. "\n"

[Peter Faller]

Thanks Josh - adding 'require 'puppet'' does solve it!
(Still a bit mysterious as to why it makes a difference; but this is 
something I only need temporarily, so that's OK)

On Thursday, 11 January 2018 21:33:21 UTC+2, Josh Cooper wrote:
>
>
>

-- 
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/3dd813e7-83b3-48d7-a44b-b3afa9d388f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PSON.load fails when string contains e.g. "\n"

[Peter Faller]

I'm trying to preprocess some version 3.x catalogs to eliminate some false 
positives reported by 'puppet catalog diff'. I copied some code from the 
catalog diff source, and have ended up with (extraneous details omitted):

#! /usr/bin/env ruby
require 'puppet/external/pson/pure'
require 'fileutils'

r = ARGV[0]
unless File.exist?(r)
raise "Cannot find resources in #{r}"
end

puts "Processing file: #{r}"
case File.extname(r)
when '.yaml'
hash = YAML.load(File.read(r))
when '.marshal'
hash = Marshal.load(File.read(r))
when '.pson'
hash = PSON.load(File.read(r))
when '.json'
hash = PSON.load(File.read(r))
else
raise "Provide catalog with the appropriate file extension, valid 
extensions are pson, yaml and marshal"
end

puts hash

I have two test files that 'puppet catalog diff' can read successfully, 
with the only difference being the presence of '\n':

[root@tstpuppet01 ~]# diff test_file1.pson test_file2.pson 13c13 < 
"content": "#!/bin/sh\nPRETEND_NCM_SSH_TRUST_IS_VALID=YES\n", --- > 
"content": "#!/bin/shPRETEND_NCM_SSH_TRUST_IS_VALID=YES", 

'puppet catalog diff' can read both files without problems.

When I try to read these files with the code above, I get the following:

[root@tstpuppet01 ~]# /usr/bin/ruby 
-I/opt/puppetlabs/puppet/lib/ruby/vendor_ruby ./preprocess.rb 
test_file1.pson Using pure library for PSON. Processing file: 
test_file1.pson Exception `NoMethodError' at 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:183
 
- undefined method `[]' for nil:NilClass Exception `PSON::GeneratorError' 
at 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:201
 
- Caught NoMethodError: undefined method `[]' for nil:NilClass 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:183:in
 
`block in parse_string': Caught NoMethodError: undefined method `[]' for 
nil:NilClass (PSON::GeneratorError) from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:182:in
 
`gsub' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:182:in
 
`parse_string' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:216:in
 
`parse_value' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in
 
`parse_object' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in
 
`parse_value' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in
 
`parse_object' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in
 
`parse_value' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:246:in
 
`parse_array' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:220:in
 
`parse_value' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in
 
`parse_object' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:225:in
 
`parse_value' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:280:in
 
`parse_object' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/pure/parser.rb:92:in
 
`parse' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/common.rb:125:in
 
`parse' from 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/external/pson/common.rb:259:in
 
`load' from ./preprocess.rb:21:in `' 

The file without '\n' reads OK:

[root@tstpuppet01 ~]# /usr/bin/ruby 
-I/opt/puppetlabs/puppet/lib/ruby/vendor_ruby ./preprocess.rb 
test_file2.pson 
Using pure library for PSON.
Processing file: test_file2.pson
{"document_type"=>"Catalog", "data"=>{"resources"=>[{"type"=>"File", 
"title"=>"/etc/opt/rim/develop.sh", "tags"=>["file", "class", "rimcdm"], 
"file"=>"/etc/puppet/environments/trunk_9_4_0_0/modules/rimcdm/manifests/init.pp",
 
"line"=>219, "exported"=>false, 
"parameters"=>{"content"=>"#!/bin/shPRETEND_NCM_SSH_TRUST_IS_VALID=YES", 
"backup"=>"main"}}], "edges"=>[{"source"=>"Stage[main]", 
"target"=>"Class[Settings]"}], "classes"=>["settings"]}, 
"metadata"=>{"api_version"=>1}}

Can anyone spot the difference between what 'puppet catalog diff' does to 
read PSON, and what the code above does?

-- 
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/2503d182-0c13-4543-ab9f-08f5852abb5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Misplaced Web Page (jenkins ci_reporter rspec)

[Peter Berghold]

Just a week or two ago I found (re-found?) a web page that laid out all the
steps necessary to incorporate ci_reporter and publish RCOV test results.
Can't find it now.  Anybody got the link for that?
Trying to add this functionality to the Jenkins pipeline that publishes my
modules to our testing environment.

-- 
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/CAArvnv0VHqK0T41fWqeL_iM%3DTPVumEEG9w4Afj__8NvXwEhH-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Conditional actions based on result of other actions?

[Peter Faller]

Puppet resources have metaparameters like 'notify', 'subscribe', 'before', 
'require' that make it possible to make things happen in the desired 
sequence; so it is possible to have 'exec' resources that trigger on some 
conditions.

It might be going a bit beyond the intention of Puppet; but you could 
create a file if an error occurs, and then test using 'onlyif' in an 'exec' 
to create a ticket if the file exists.

Or you can create custom modules and implement the logic in Ruby code.

On Wednesday, 20 December 2017 15:35:56 UTC+2, buoyant_puppy wrote:
>
> How can I get the result of an action and use it conditionally in my code? 
> As a very simple example:
>
> package { "wget" : ensure => 'present' }
> # if that failed, do X
>
> To put this in context, some actual use cases I have:
> - attempt to register an agent to a remote service and if that fails, open 
> a ticket via an API so it can be manually resolved
> - attempt to create an LV and if that fails, call another module that adds 
> some new LUNs to my host, extend VG etc...
> - ensure some critical service is running, but in case of any error raise 
> an alert via the standard alert API
> - when applying some security-related code, confirm success/failure to a 
> compliance product API
>
>
>

-- 
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/37c1fc2b-c5d2-4269-8a75-7b1cb10215e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Duplicate declaration error - what's the correct approach to avoid this?

[Peter Faller]

On Thursday, 23 November 2017 16:47:44 UTC+2, buoyant_puppy wrote:
>
> Why does this:  
>   class mymodule {
> notify { "booboo": }
> notify { "booboo": }
>
> provoke the error:
>   Error while evaluating a Resource Statement, Duplicate declaration: 
> Notify[booboo] is already declared in file 
>
> The error occurs because you have two resources of the same type (notify) 
with the same name ('booboo'). Remember that 'notify' is not like a 
'log.info' - it is a resource in it's own right, and each 'notify' has to 
have a unique name.

 

> That's is a simplified version of my actual use case:
>   $mythings.each | String $x | {# for each x in list 'mythings'
> notify { "gonna do something with $x": }
>   
>
> In plain english, for example, I may have a list of rpms and want to loop 
> through them to ensure all are installed.
>
> What would be the correct way to do this, if not the above?
>
> Your code looks OK- as long as you don't have duplicates in $mythings. 
What is the output you get from your actual use case? 

-- 
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/8dfb2faf-e769-4682-9de4-d1b55d04664d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Set environment variable for Service resource

[Peter Faller]

In general, I'd say you would have to put the variables into a 
configuration file for the service (via a template, or an augeas resource), 
or if the service is managed by systemd, in the relevant '???.service' file.

On Tuesday, 7 November 2017 16:27:39 UTC+2, Andrei wrote:
>
> Hello,
> is there a way to configure a set of environment variables to be available 
> to a Service resource similar to what Exec supports? 
>
>

-- 
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/02333d31-1f73-4abf-8f9d-1c0146397790%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Clean Puppet 3 to Puppet 4 migration

[Peter Souter]

One of the useful tools for an upgrade situation is the Catalog Preview 
tool. It requires Puppet 3.8, which should be a much smaller jump for you 
(3.7 -> 3.8) to begin with. It'll probably help soothe worries for the ops 
team by allowing a level of testing and certainty before the big jump.

It's pretty rad, because it will compile catalogs in the Puppet 3 format, 
and compare them with catalogs compiled with "future parser" turned on, 
which was the Puppet 4 compatibility mode avaliable for Puppet 3 for 
helping to upgrade.

Setup steps are here: https://forge.puppet.com/puppetlabs/catalog_preview

Another tool that's used is Githubs Octocatalog-diff
 https://github.com/github/octocatalog-diff 
, which is similar to 
catalog-preview

**I generally recommend a cutover to a completely new 
infra, rather than trying to upgrade in place. This is more philosophical 
than technical, as it's probably easier if you have the server resources to 
create a new shiny Puppet 4 infra, then slowly just point old servers to 
the new shiny servers in batches, picking the easiest or least breaking 
servers first (eg. lab, dev, canary servers for testing) rather than trying 
to big-bang upgrade everything at once and worrying about rollback. But I 
know this can be a harder battle with change windows and getting everyone 
aligned.**

In terms of automation, the new Bolt tool would be perfect for you here, as 
you can use bolt to run the commands needed to move servers to the new 
infra. 

We have a bootstrap task 
 avaliable, but right 
now it's PE only (it uses a particular script we host to bootstrap Puppet, 
open-source support is coming in the future) but it wouldn't be too hard to 
just use bolt to either run a script (Such as my
 https://github.com/petems/puppet-install-shell 
) or write your own 
organisational specific task to do the steps you need, and rollback if 
something goes wrong.

I'd also recommend the following talks and blogposts about Puppet 3->4 
upgrades:

   - Rob Nelsons talk about AT's upgrade from PuppetConf 2016 (
   https://www.youtube.com/watch?v=FWnj0xQOZN8)
   - Nacho Barrientos talk about CERN's Puppet 4 update (
   
https://puppetconf17.sched.com/event/B4wI/a-not-so-bumpy-road-to-puppet4-at-cern-nacho-barrientos-cern
 Vids 
   not out yet, soon!)
   - Skroutz's blogpost about their upgrade (
   https://engineering.skroutz.gr//blog/upgrading-puppet3-to-puppet4/
   - Githubs blogpost about their Puppet 4 Upgrade: 
   https://puppet.com/blog/upgrading-to-puppet-4-at-github
   
There's also the #upgraders room on the Puppet Slack channel if you have 
other questions :) Feel free to ping me there with questions, if I'm around 
I might be able to help (@petems)

On Wednesday, October 11, 2017 at 9:15:02 PM UTC+1, Michael Watters wrote:
>
> Been through a similar upgrade myself.  The first step would be to spin up 
> a new puppet master running Puppet Server.  You can copy over the SSL dir 
> from your old/current master to avoid SSL errors on the agents.  For 
> testing you'll want to make sure your manifests work correctly using the 
> future parser, that can be enabled in the puppet.conf file on the agents.  
> Setting up a separate environment for testing is also recommended.
>
> Puppet Server will work with 3.7 clients so once you have a manifest that 
> compiles correctly you can just point the agents to the new master's IP.
>
>
> On Wednesday, October 11, 2017 at 8:07:13 AM UTC-7, Salty Old Cowdawg 
> wrote:
>>
>> About three years ago (4 years ago?) I deployed a Puppet infrastructure 
>> for my company and department based on FOSS Puppet 3.7.   Given that's been 
>> deprecated of course I'm very much looking to migrate to Puppet 4.   
>> Besides for about three months I worked for another company and got spoiled 
>> by Puppet 4. 
>>
>> So I'm back at my old digs and assessing what it will take to go from P3 
>> to P4.   Here are some of the things I have to think about
>>
>> 1) the migration needs to be fully automated both on the server end and 
>> the client end. 
>> 2) no really this is going to be done by operations personnel who 
>> have a low threshold of fright for Puppet in spite of my best efforts to 
>> desensitize them.
>> 3) There is as penetrable firewall between me (developer) and the Puppet 
>> infrastructure servers and clients so I cannot personally intervene
>>
>> Anybody out there been through this pain and have any suggestions and 
>> pointers on how to make this happen with minimal "breakage?" 
>>
>

-- 
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 

[Puppet Users] Re: SSL_read:: shutdown while in init error

[Peter Souter]

Hi folks, I saw Vishal's question over on StackOverflow 
,
 
and googling it came back to here!

I answered Vishal over on SO, but thought I'd post it here for Maxim also 
and close the loop:

It seems like there was a breaking change brought in when updating the 
OpenSSL package with older Puppet 3. Puppet 3 itself is EOL since December 
of 2016, so I recommend you update to Puppet 4 or even 5, which came out 
this year.

Another benefit: Puppet 4 and onward bundles it's own openssl, so you don't 
have to worry about breaking Puppet when upgrading openssl (See puppet-agent: 
What is it, and what's in it? 
)

You can do so with my helper script:

wget -O - 
https://raw.githubusercontent.com/petems/puppet-install-shell/master/install_puppet_agent.sh
 | sudo sh

Or manually:

Puppet 5

rpm -ivh http://yum.puppetlabs.com/puppet5/puppet5-release-el-6.noarch.rpm
yum install puppet-agent -y

Puppet 4

rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-pc1-el-6.noarch.rpm
yum install puppet-agent -y


On Thursday, October 12, 2017 at 3:39:54 PM UTC+1, Vishal Bhalla wrote:
>
> Yup - we are seeing similar problems.
>
> After our client Amazon Linux boxes updated to latest OpenSSL (SL 
> 1.0.2k-fips  26 Jan 2017) we now see 
>
> Error: SSL_read:: shutdown while in init
>
> On puppet runs. Only way we could work around it was to perform a yum 
> rollback :(
>
> On Monday, 9 October 2017 12:48:09 UTC+1, Maxim Nikolaev wrote:
>>
>> Hi
>>
>> I'm using puppet agent 3.8.7 with puppetserver 2.8. Everything worked 
>> fine for long period.
>> This week we set update on openssl (version 
>> openssl-1.0.2k-7.103.amzn1.x86_6).
>> After that we started to get errors on puppet run:
>>
>>
>>
>>
>>
>> *Error: Could not set 'file' on ensure: SSL_read:: shutdown while in 
>> initError: Could not retrieve catalog from remote server: SSL_read:: 
>> shutdown while in init*I tried to play with pupptserver and puppet agent 
>> config.
>>
>> Added http_keepaalive_timout and set larger body-max-size. 
>>
>> This resolve issue on existing servers. But each time I run puppet first 
>> time - I see this again.
>> For ex, when I try to create Packer image - it always fail, because of this 
>> errors.
>>
>> I've looked for similar errors, but find nothing.
>>
>> Have someone experienced same problem?
>>
>> Thanks.
>>
>>
> --
>
> *This email was sent by a company owned by Financial Times Group Limited 
> ("FT Group "), 
> registered office at Number One Southwark Bridge, London SE1 9HL.  
> Registered in England and Wales with company number 879531. This e-mail may 
> contain confidential information. If you are not the intended recipient, 
> please notify the sender immediately, delete all copies and do not 
> distribute it further.  It could also contain personal views which are not 
> necessarily those of the FT Group.  We may monitor outgoing or 
> incoming emails as permitted by law.*
>

-- 
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/d90b922a-56d4-4d55-95fd-e44eb8ea8201%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Peter Meier]

> There still a leak on Trocla database connections (latest
> gem/module/hiera backend).
> 
> I've installed a puppetserver, with only a node connected on; after 5
> days, there is 240 opened connections.

So, as you were changing a lot (new gem, module and switching to new
backend) I'm not sure whether you are still the facing exactly the same
issue as at the beginning, but just a different variant of it.

But so let's focus on the current situation as it is the one with
everything up-to-date.

I dumped the situation and my current guess on what is going wrong in
the module's issue tracker:

https://github.com/duritong/puppet-trocla/issues/25

As you have a single node in on environment that reproduces the problem
I would be happy if you could provide in the ticket more information,
specifically regarding to:

* How does your hiera config look like atm., so how is the trocla
backend hooked into the hierarchies
* How many classes does the node include during compilation
* How many class parameters are triggering the trocla backend?
* is the amount of connections growing over time, even if you don't
change anything (no new puppet code or something like that).

Estimated numbers are fine, but they should get an indication whether we
have too many caches that all keep connections open, while the actual
idea was to use the caches to not open too many connections.

thanks and best

~pete

-- 
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/cff3445a-3c2e-c115-3a14-1d5ec51e3a30%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Clean Puppet 3 to Puppet 4 migration

[Peter Berghold]

About three years ago (4 years ago?) I deployed a Puppet infrastructure for
my company and department based on FOSS Puppet 3.7.   Given that's been
deprecated of course I'm very much looking to migrate to Puppet 4.
Besides for about three months I worked for another company and got spoiled
by Puppet 4.

So I'm back at my old digs and assessing what it will take to go from P3 to
P4.   Here are some of the things I have to think about

1) the migration needs to be fully automated both on the server end and the
client end.
2) no really this is going to be done by operations personnel who have
a low threshold of fright for Puppet in spite of my best efforts to
desensitize them.
3) There is as penetrable firewall between me (developer) and the Puppet
infrastructure servers and clients so I cannot personally intervene

Anybody out there been through this pain and have any suggestions and
pointers on how to make this happen with minimal "breakage?"

-- 
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/CAArvnv0END3xCwQsNwK9jjkSEq37LvY%3Dy-Ck7johj5Af3GHgWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Peter Meier]

> We are on hiera v3, we only tuned  "max-requests-per-instance: 5000"
> because of a databases connection leak with our Trocla library.

This is fixed with the trocla module 1.0.1 [1] are you on that version?

best

~pete

[1]
https://github.com/duritong/puppet-trocla/commit/bbedb788a7951e2f69c1c2815a5c3c669ff02ae6

-- 
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/e586fee5-028c-bc30-6758-5190c487010f%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: puppetserver-acces.log

[Peter Krawetzky]

So I recycled the puppetserver service and it now appears the log is back 
to normal size over the course of time.  I'm guessing something happened to 
cause puppetserver to dump more than it should have.

On Monday, October 2, 2017 at 10:24:19 AM UTC-4, Peter Krawetzky wrote:
>
> We had an odd situation happen earlier this morning.  Puppet server 
> version 2.1.1 on RHEL7.
>
> I have 4 puppet servers behind a load balancing F5 server.  One of our 
> puppet servers puppetserver-access.log grew (over 2TB's) to the point that 
> it almost filled /var which for a server is not good.  I don't see anything 
> different in this log compared to the other 3 servers.  Does anyone know 
> what would cause this log to grow?  Is there a way to turn it off as I 
> don't see that in the documentation?
>
> I watched the F5 balancing and it was distributing all workload across all 
> 4 servers correctly.  I also restarted the puppetserver service on this on 
> server to see if maybe something was stuck.  Because there is so much data, 
> it's extremely hard to see any patterns.
>
> Thanks in advance for any assistance.
>

-- 
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/ae6fe59e-6aad-4919-9c02-4bcdbb619da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppetserver-acces.log

[Peter Krawetzky]

Since I don't have a setting in the file, it defaults to info.  Unless 
there is a bug. 

On Monday, October 2, 2017 at 10:24:19 AM UTC-4, Peter Krawetzky wrote:
>
> We had an odd situation happen earlier this morning.  Puppet server 
> version 2.1.1 on RHEL7.
>
> I have 4 puppet servers behind a load balancing F5 server.  One of our 
> puppet servers puppetserver-access.log grew (over 2TB's) to the point that 
> it almost filled /var which for a server is not good.  I don't see anything 
> different in this log compared to the other 3 servers.  Does anyone know 
> what would cause this log to grow?  Is there a way to turn it off as I 
> don't see that in the documentation?
>
> I watched the F5 balancing and it was distributing all workload across all 
> 4 servers correctly.  I also restarted the puppetserver service on this on 
> server to see if maybe something was stuck.  Because there is so much data, 
> it's extremely hard to see any patterns.
>
> Thanks in advance for any assistance.
>

-- 
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/e8fd7154-9f69-4234-8376-9a6f9c056640%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppetserver-acces.log

[Peter Krawetzky]

We had an odd situation happen earlier this morning.  Puppet server version 
2.1.1 on RHEL7.

I have 4 puppet servers behind a load balancing F5 server.  One of our 
puppet servers puppetserver-access.log grew (over 2TB's) to the point that 
it almost filled /var which for a server is not good.  I don't see anything 
different in this log compared to the other 3 servers.  Does anyone know 
what would cause this log to grow?  Is there a way to turn it off as I 
don't see that in the documentation?

I watched the F5 balancing and it was distributing all workload across all 
4 servers correctly.  I also restarted the puppetserver service on this on 
server to see if maybe something was stuck.  Because there is so much data, 
it's extremely hard to see any patterns.

Thanks in advance for any assistance.

-- 
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/67355598-c726-4d24-be0a-bb55166f3576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

[Peter Berghold]

I was afraid that would be an answer I got... :-)

There are plans to move to Puppet 4 where I know all this works but given I
have to support all this on RHEL 6.x there may be some obstacles there.   I
would LOVE to wave a magic wand and make Puppet 3.x go away

So.. 3.8 eh?  There's something to investigate


On Tue, Sep 26, 2017 at 1:46 PM Rob Nelson <rnels...@gmail.com> wrote:

> If I had to guess, it would be that the merge settings either don't exist
> or are buggy in 3.7.2. 3.8 was EOL in December last year, if you have to
> stick with 3 I'd suggest at least trying it with 3.8.
>
> On Tue, Sep 26, 2017 at 12:35 PM Peter Berghold <salty.cowd...@gmail.com>
> wrote:
>
>> Seeing things like doing a hiera lookup inside a manifest such as
>>
>> $somevar = hiera('randomvalue','notfound')
>>
>> returning nils and other odd behavior.
>>
>> I have a hiera.yaml file that looks like:
>>
>> ---
>> :backends:
>>   - yaml
>> :merge_behavior: deeper
>> :deep_merge_options: {}
>> :yaml:
>>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
>> :hierarchy:
>>   - "function/${::facts.host_function}"
>>   - "datacenter/%{::facts.sitename}"
>>   - "nodes/%{fqdn}"
>>   - "common_classes"
>>   - "common"
>>
>> and yet I see both the nodes and common_classes being ignored.
>>
>> Of more concern to me is I'm trying to set values such as
>>
>> somemod::parms::value1:  somevalue
>>
>> and that's being ignored.
>>
>> Puppet.conf is configured correctly because it *is* finding a class list
>> in common.yaml but nowhere else.
>>
>>
>> Thoughts?
>>
>> --
>> 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/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Rob Nelson
>
> --
> 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/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6GYnQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6GYnQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAArvnv1Mnqs1B_ZAUUFSb1xSifUu6X%2Birj41C9j1UJa%2Bprg2QQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

[Peter Berghold]

Seeing things like doing a hiera lookup inside a manifest such as

$somevar = hiera('randomvalue','notfound')

returning nils and other odd behavior.

I have a hiera.yaml file that looks like:

---
:backends:
  - yaml
:merge_behavior: deeper
:deep_merge_options: {}
:yaml:
  :datadir: "/etc/puppet/environments/%{environment}/hieradata"
:hierarchy:
  - "function/${::facts.host_function}"
  - "datacenter/%{::facts.sitename}"
  - "nodes/%{fqdn}"
  - "common_classes"
  - "common"

and yet I see both the nodes and common_classes being ignored.

Of more concern to me is I'm trying to set values such as

somemod::parms::value1:  somevalue

and that's being ignored.

Puppet.conf is configured correctly because it *is* finding a class list in
common.yaml but nowhere else.


Thoughts?

-- 
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/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Using SRV records...

[Peter Berghold]

Doesn't seem to be working for me in Puppet 3.7... should it?

I followed instructions from this page:
https://docs.puppet.com/puppet/3/scaling_multiple_masters.html

Had my support team setup records for three domains, have a test machine
pointing to one of them and it fails to find the Puppet master.

Checked using "dig -t srv" and the record resolves so I'm rather baffled at
the moment.

-- 
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/CAArvnv1d54FpsPgXkCCscC5X_UsM8WrxFWrqwhv%2BqJLOoGtBLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB Upgrade Question from 2.1.1-1 to 2.7.2-1

[Peter Krawetzky]

I'm doing a minor upgrade from 2.1.1-1 to 2.7.2-1 and was wondering if the 
size of the database makes a difference in how long the upgrade takes? 
 It's currently managing approximately 3200+ nodes in production.  Testing 
in our lab environment did not run long as we only manage about 500 nodes 
there.  Was wondering if there is a correlation between the number of nodes 
and the upgrade process since it's really not described well in the 
documentation.

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/81457007-c2f1-4775-ad21-d55415901d8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Unable to diff catalogs - undefined method 'version'

[Peter Faller]

Even when trying to compare a minimal catalog ('node 
tstpuppet01.localdomain {}') to itself, I get an error:

# puppet master --environment trunk_9_4_0_0 --compile 
tstpuppet01.localdomain > /tmp/tstpuppet01.localdomain.new.pson
# puppet catalog diff --debug tstpuppet01.localdomain.new.pson 
tstpuppet01.localdomain.new.pson
Debug: Runtime environment: puppet_version=5.0.1, ruby_version=2.4.1, 
run_mode=user, default_encoding=UTF-8
Error: Add --debug for realtime output, add --render-as {json,yaml} for 
parsed output
Error: undefined method `version' for # 
<<<<--
Error: Try 'puppet help catalog diff' for usage

Is this a versioning issue, perhaps? I'm using:

[root@tstpuppet01 tmp]# puppet --version
5.0.1
[root@tstpuppet01 tmp]# puppet module list
/etc/puppetlabs/code/environments/production/modules (no modules installed)
/etc/puppetlabs/code/modules
├── crayfishx-firewalld (v3.3.2)
├── example42-network (v3.3.7)
├── herculesteam-augeasproviders_core (v2.1.3)
├── herculesteam-augeasproviders_ssh (v2.5.3)
├── puppetlabs-concat (v4.0.1)
├── puppetlabs-firewall (v1.9.0)
├── puppetlabs-limits (v0.1.0)
├── puppetlabs-ntp (v6.2.0)
├── puppetlabs-stdlib (v4.19.0)
└── zack-catalog_diff (v1.6.0)
/opt/puppetlabs/puppet/modules (no modules installed)

Anyone seen this?

- Peter

-- 
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/3331ac0c-7d9c-4a98-aeef-8d3779ab675f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PDK 1.0.0.1 on Windows

[Peter Faller]

Thanks David - the combination of rspec-puppet-facts and 
'operatingsystem_support' 
in metadata.json makes it work.

On Thursday, 17 August 2017 18:22:24 UTC+2, David Schmitt wrote:
>
> 
>

-- 
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/30af0aee-bf13-453a-b70a-f9738cba25e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PDK 1.0.0.1 on Windows

[Peter Faller]

Hi David

Reduced example manifest and test attached ... 

On Linux:

[root@tstpuppet01 rimcdm]# rspec spec/defines/test_reduced_spec.rb 
.

Finished in 0.79952 seconds (files took 2.66 seconds to load)
1 example, 0 failures

On Windows:

PS rimcdm> pdk bundle exec -- rspec .\spec\defines\test_reduced_spec.rb
F

Failures:

  1) rimcdm::test_reduced Create Test environment should compile into a 
catalogue without dependency cycles
 Failure/Error: is_expected.to compile
   error during compilation: Parameter path failed on 
File[/var/lib/tftpboot]: File paths must be fully qualified, n
ot '/var/lib/tftpboot' at line 3
 # ./spec/defines/test_reduced_spec.rb:18:in `block (3 levels) in '

Finished in 8.33 seconds (files took 2.02 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/defines/test_reduced_spec.rb:17 # rimcdm::test_reduced Create 
Test environment should compile into a catalo
gue without dependency cycles


On Thursday, 17 August 2017 15:32:49 UTC+2, David Schmitt wrote:
>
> ...
>

-- 
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/8fad49d4-5efd-44c2-b3c0-49627c21d329%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


test_reduced.pp
Description: Binary data


test_reduced_spec.rb
Description: Binary data

Re: [Puppet Users] PDK 1.0.0.1 on Windows

[Peter Faller]

Hi David

Thanks for pointing out 'pdk bundle' - it does provide what I was looking 
for. It is however a bit noisy (but that's not a big deal):

PS> pdk bundle exec -- rspec .\spec\classes\apg_base_spec.rb
.

Finished in 7.81 seconds (files took 1.85 seconds to load)
1 example, 0 failures

C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows
/api_types.rb:6: warning: already initialized constant FFI::WIN32_FALSE
C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows
/api_types.rb:5: warning: previous definition of WIN32_FALSE was here
C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows
/api_types.rb:9: warning: already initialized constant FFI::ERROR_SUCCESS
C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows
/api_types.rb:8: warning: previous definition of ERROR_SUCCESS was here
C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows
/api_types.rb:21: warning: already initialized constant 
FFI::Pointer::NULL_HANDLE
C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows
/api_types.rb:20: warning: previous definition of NULL_HANDLE was here
!! spec/fixtures/modules/rimcdm already exists and is not a symlink 


The things that I use 'rake' and 'rspec' for are:

> rspec spec/classes/some_class_spec.rb # to run a single unit test instead 
of all tests
> rake spec_prep # to update fixtures
> rake spec_standalone # to run tests without updating fixtures

I'm working on refactoring an over-sized module; that's why being able to 
do quick tests is important to me.

I'm using the version of rspec-puppet bundled with the PDK - it appears to 
be version 2.6.7:

PS> pdk bundle exec -- rspec --debug
...
# C:/Program Files/Puppet 
Labs/DevelopmentKit/share/cache/ruby/2.1.0/gems/rspec-puppet-2.6.7/lib/rspec-puppet/monkey_patches.rb:273:in
 
`require'
...

On Thursday, 17 August 2017 10:33:08 UTC+2, David Schmitt wrote:
>
> 
>

-- 
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/50c77961-3246-47d3-bba8-1ff1a9d2cd78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PDK 1.0.0.1 on Windows

[Peter Faller]

While trying to use the PDK on Windows (instead of using a Linux VM for 
development), I've come across a few hitches:

1) 'rake' is not available as a command (it is accessible via 
$env:DEVKIT_BASEDIR/private/private\ruby\2.1.9\bin\rake though)
2) 'rspec' is not available as a command
3) errors related to file paths (seems to be an old Windows-related 
issue): Parameter path failed on File[/tftpboot]: File paths must be fully 
qualified, not '/tftpboot' at line 4

Are there any workarounds for these?

(BTW: Initially I had a standard Ruby 2.1 install in my PATH - that caused 
a lot of trouble too.)

-- 
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/238147f7-36e6-4a8f-998e-4f2570e68c91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [ANN] Puppet Development Kit (pdk) 1.0

[Peter Faller]

BTW: changing line 3 in C:\Program 
Files\WindowsPowerShell\Modules\PuppetDevelopmentKit\PuppetDevelopmentKit.psm1 
to:

$env:PATH   = "$($env:DEVKIT_BASEDIR)\bin;"+$env:PATH

... fixes it.

On Wednesday, 16 August 2017 14:06:23 UTC+2, Peter Faller wrote:
>
> ...
>
>>

-- 
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/3b097124-1e80-4621-ba6b-a7e8d1f21c44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [ANN] Puppet Development Kit (pdk) 1.0

[Peter Faller]

Seems to be a hitch with the Windows install on Windows 8.1: I installed 
pdk-1.0.0.1-x64.msi; opened a new powershell window, and found that while 
pdk works, the PATH is wrong:


modules> $env:path
C:\Program Files\Puppet Labs\DevelopmentKit\\bin;%PATH%

Any tips on how to correct this?

On Tuesday, 15 August 2017 22:51:52 UTC+2, Lindsey Smith wrote:
>
> 
>

-- 
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/0aeb7ba1-48c7-4668-b5d9-d861d9d33fb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: facter details copy to central location

[Peter Faller]

Have you looked at Puppet DB?

(There's also a record of facts in /var/lib/puppet/yaml/facts/ 
for Puppet 3.x - might be available in Puppet 4 and 5 too.)

On Tuesday, 25 July 2017 16:59:31 UTC+2, Amber Mehra wrote:
>
> Hey Guys,
>
> I have certain requirement to get puppet client inventory like "facter 
> operatingsystem, facter ipaddress, etc : copied all details to some where 
> in file on Puppet master server .
>
> Please advise
>

-- 
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/83f88c97-91c6-4759-9a4c-d9d2a8e1802a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Upgraded puppet server and hiera is not working

[Peter Krawetzky]

I upgraded the puppet server from 2.1.1-1 to 2.7.2-1 and at the same time 
the puppet agent was upgraded from 1.2.2-1 to 1.10.4-1.

I read several different posts on this forum and others but I can't seem to 
get hiera 5 to work properly.  I tried a couple of different hiera.yaml 
config files yet nothing seems to work correctly.  I've tried to use the 
old hiera.yaml version and getting the expected depricated warning.  The 
Puppet doci on V5 and converting is not the greatest.

Our hiera config uses both json files and couchdb.  Everytime I run puppet 
lookup I get:
[root@xlabsvcpup4 code]# puppet lookup pup_url
Warning: /etc/puppetlabs/code/hiera.yaml: Use of 'hiera.yaml' version 3 is 
deprecated. It should be converted to version 5
   (in /etc/puppetlabs/code/hiera.yaml)
Warning: Undefined variable '::my_role';
   (file & line not available)
Error: Could not run: HTTP request path is empty

Current hiera.yaml file:
[root@xlabsvcpup4 code]# cat hiera.yaml
---
:backends:
  - http
  - json
  - yaml
:hierarchy:
  - "%{::clientcert}"
  - "%{::environment}/%{::clientcert}"
  - "%{::environment}/%{::my_role}"
  - "%{::environment}/common"
  - "%{::my_role}"
  - common
:json:
  :datadir: /u01/hieradata/
:yaml:
  :datadir: /u01/hieradata/
:http:
  :host: couchdb.com
  :port: 5984
  :output: json
  :failure: graceful
  :use_auth: true
  :auth_user: 'userid'
  :auth_pass: 'password'
  :paths:
- /hieradb/%{::clientcert}
- /%{::environment}/%{::my_role}
- /%{::environment}/common
- /hieradb/%{::my_role}
- /hieradb/common

I tried to use this version 5 config file:
---
version: 5

defaults:
  datadir: "/u01/hieradata"
  data_hash: json_data

hierarchy:
  - name: "json files"
paths:
- "%{::clientcert}.json"
- "%{::environment}/%{::clientcert}.json"
- "%{::environment}/%{::my_role}.json"
- "%{::environment}/common.json"
- "%{::my_role}.json"
- common.json
  - name: "Couchdb"
options:
connections:
hiera3_backend: hiera-http
host: couchdb.com
output: json
failure: graceful
use_auth: true
auth_user: 'userid'
auth_pass: 'password'
paths:
   - /hieradb/%{::clientcert}
   - /%{::environment}/%{::my_role}
   - /%{::environment}/common
   - /hieradb/%{::my_role}
   - /hieradb/common
When I use the V5 config i get:
Warning: Undefined variable '::my_role';
   (file & line not available)
Error: Could not run: 'json_data' one of 'path', 'paths' 'glob', 'globs' or 
'mapped_paths' must be declared in hiera.yaml when using t


-- 
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/c18c3f70-d65b-4de9-96b1-d56602b782e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB Curl Queries

[Peter Krawetzky]

Isn't that for the PE version?  we are using open source.

On Tuesday, July 11, 2017 at 11:48:35 AM UTC-4, Peter Krawetzky wrote:
>
> Using CURL to query PuppetDB has got to be the most time consuming thing 
> I've ever done.  It took me almost 3 hours one day to create a CURL query 
> that I ended up creating in a SQL statement in 10 minutes once I figured 
> out the database structure.
>
> Does anyone have:
>
>1. A documented list of CURL queries and the syntax
>2. A documented list of SQL queries to directly against the Postgresql 
>database
>
>
>

-- 
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/a8be2d5d-f224-46b5-b72d-97338b24d44e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB Curl Queries

[Peter Krawetzky]

Using CURL to query PuppetDB has got to be the most time consuming thing 
I've ever done.  It took me almost 3 hours one day to create a CURL query 
that I ended up creating in a SQL statement in 10 minutes once I figured 
out the database structure.

Does anyone have:

   1. A documented list of CURL queries and the syntax
   2. A documented list of SQL queries to directly against the Postgresql 
   database


-- 
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/8d8e9b09-0c05-4ae8-afcf-48d6a83f8247%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Failed require resolution from RSpec.

[Peter Berghold]

I have a module that I'm refactoring that manages NTP servers and clients.
The client portion of the module performs a puppetdb (Forge Module
dalen-puppetdbquery) lookup to find the local NTP stratum 2 servers to
populate into the client's /etc/ntp.conf file.  Works great in real life
but the module fails spec testing with an error:

Failure/Error: require 'puppet/util/puppetdb'

I am using the bundler to load necessary gem files locally.   Here is my
Gemfile:

source 'https://rubygems.org'

puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" :
['>= 3.3']
gem 'puppet', puppetversion
gem 'puppetlabs_spec_helper', '>= 0.1.0'
gem 'puppet-lint', '>= 0.3.2'
gem 'facter', '>= 1.7.0'
gem 'rspec', '>= 0.0.0'
gem 'puppetdb-ruby'
gem 'puppetdb-terminus'
gem 'puppetdb_query'
gem 'ruby-puppetdb'
gem "simplecov-rcov"
gem "ci_reporter"


So, what am I 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 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/CAArvnv0s2xH4hh0dKPZPECj41RKcOnAFXgkaip7dhPrQJMthpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: parameters and hiera

[Peter Berghold]

OK... that calms my concerns a lot.

I have a second Puppet infrastructure that I'm about to build out that I'm
considering not putting Foreman on it at all.  Reason being it is going to
be in an environment where there won't be connectivity to 80/443 at all
from outside the environment.

On Mon, Jul 10, 2017 at 11:54 AM Gavin Williams  wrote:

> This is exactly how we use Foreman & Hiera in our installation...
>
> The key thing to set is when configuring the Puppet classes in Foreman,
> the 'Use Puppet Default' or 'Override' box needs to be checked.
> This means that if no values are stored in Foreman, then no value will be
> provided to Puppet, and Puppet will then use Hiera to look that value up.
>
> If you don't check that box, then you run the risk of providing empty
> strings to Puppet, thereby skipping the Hiera lookup :)
>
> HTH
>
> Gav
>
>
> On Monday, 10 July 2017 16:44:32 UTC+1, Salty Old Cowdawg wrote:
>>
>> In the shop that I code for these days we have The Foreman ENC set up and
>> running.  I want to add hiera to the mix but allow our operations folks the
>> options the ability to change parameter values using the Foreman GUI.
>> Given the applications we are having Puppet manage this is rather mandatory
>> since the values in question get changed often enough to deal with changes
>> in the operational conditions as they change.  Having operators edit hiera
>> YAML files is not a desired thing.
>>
>> I have some ideas for how to implement this but would like some input
>> from others that may have dealt with the same thing.  What I'm looking for
>> is a coding pattern that says "if foreman is blank, use hiera and if hiera
>> is blank use this default."
>>
>> thoughts anybody?
>>
>> --
> 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/311ba2bb-87a6-4c73-905b-339bed9dd779%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAArvnv2gKBVh6FF%2BM8Gp90ebeONFNVdtGk6nnKFDjVO6TUOxiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB low catalog-duplication rate Puppet DB 4.3.0

[Peter Krawetzky]

Yes I am on V4 and the query just didn't return any results - no errors so 
I assume I am using the correct curl command.  Thanks

On Wednesday, June 28, 2017 at 2:11:17 PM UTC-4, Mike Sharpton wrote:
>
> Hey all,
>
> I am hoping there is someone else in the same boat as I am.  We are 
> running Puppet 4.2.2, along with PuppetDB 4.3.0.  I am seeing low 
> duplication rate which I think is contributing to our queuing problems in 
> PuppetDB.  The queue will fluctuate from 0-100 queued, to up to 2000.  We 
> have around 4500 nodes, and we are using 8 threads on our PuppetDB server. 
>  I am seeing that the low duplication rate is caused by hashes not matching 
> and a full insert running which is expensive on the DB instead of just 
> updating the time stamp.  I don't know why these would not be matching, and 
> may need help as far as how to find something like this.  I see items in 
> PuppetDB3 for this, but not 4.  I see that using timestamp and other items 
> which change each time will cause the catalog to never be the same, but I 
> would think we would have 0% duplication if this was the case.  I am also 
> seeing that things are improved in 4.4.0 as far as performance and a 
> missing index is corrected that may speed things.  I am wondering what 
> others have done/seen with this and whether upgrading to 4.4.0 would do me 
> good.  I am thinking it would as many things appear to fixed around the 
> issues I am seeing.  Thanks in advance,
>
> Mike
>

-- 
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/d3b49873-5665-4286-bba2-b69ae304ae8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] parameters and hiera

[Peter Berghold]

In the shop that I code for these days we have The Foreman ENC set up and
running.  I want to add hiera to the mix but allow our operations folks the
options the ability to change parameter values using the Foreman GUI.
Given the applications we are having Puppet manage this is rather mandatory
since the values in question get changed often enough to deal with changes
in the operational conditions as they change.  Having operators edit hiera
YAML files is not a desired thing.

I have some ideas for how to implement this but would like some input from
others that may have dealt with the same thing.  What I'm looking for is a
coding pattern that says "if foreman is blank, use hiera and if hiera is
blank use this default."

thoughts anybody?

-- 
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/CAArvnv2hyXDTSvx_r3cdst78qy4fbG7M5bfCkJDXRMHr%2BTMwDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Compare node fact runs

[Peter Krawetzky]

Do you have a link to those posts Mike?

On Thursday, July 6, 2017 at 12:54:37 PM UTC-4, Peter Krawetzky wrote:
>
> I'm seeing a lot of replace facts in the puppetdb server log.  I googled 
> but can't find anything solid.
>
> Is there a way to compare facts for a node between runs?  Our agents run 
> hourly.  We are using open source PuppetDB 3.0.2.
>
> 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/ef0caed9-04f1-4977-afe9-deee1fc31db7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Packet Rate?

[Peter Berghold]

Has anybody out there done any sort of study on what Puppet produces in
terms of I/O packet rate?  I'm being asked to fill in a spreadsheet with
that information

-- 
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/CAArvnv3G8Lbe8GL11SGC251YYn-SjUs-KEPR2NfDjKGqzgZhEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Minor Upgrade

[Peter Krawetzky]

I need a clarification on a comment in the puppet upgrade doci.  Does this 
mean (last sentence below) I can upgrade the puppetdb servers before the 
puppetservers and puppet agent?  It's the "nodes" comment that has me 
confused.  I take that as it can go before anything.

A minor upgrade is an upgrade from one Puppet 4 release to another. The 
order in which you upgrade packages is important. Always upgrade 
puppetserver on your masters *before* you upgrade agents. *You can upgrade 
PuppetDB before or after you upgrade other nodes.*

-- 
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/074f9f65-d10b-4ab6-b544-07717b7b438e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB low catalog-duplication rate Puppet DB 4.3.0

[Peter Krawetzky]

So I went to run the curl command listed below and it came back with 
nothing.  So I used pgadmin to look at the catalogs table and it's 
completely empty.  The system has been running for almost 24 hours after 
dropping/creating the postgresql database.  Any idea why the catalog table 
would be empty?

On Wednesday, June 28, 2017 at 2:11:17 PM UTC-4, Mike Sharpton wrote:
>
> Hey all,
>
> I am hoping there is someone else in the same boat as I am.  We are 
> running Puppet 4.2.2, along with PuppetDB 4.3.0.  I am seeing low 
> duplication rate which I think is contributing to our queuing problems in 
> PuppetDB.  The queue will fluctuate from 0-100 queued, to up to 2000.  We 
> have around 4500 nodes, and we are using 8 threads on our PuppetDB server. 
>  I am seeing that the low duplication rate is caused by hashes not matching 
> and a full insert running which is expensive on the DB instead of just 
> updating the time stamp.  I don't know why these would not be matching, and 
> may need help as far as how to find something like this.  I see items in 
> PuppetDB3 for this, but not 4.  I see that using timestamp and other items 
> which change each time will cause the catalog to never be the same, but I 
> would think we would have 0% duplication if this was the case.  I am also 
> seeing that things are improved in 4.4.0 as far as performance and a 
> missing index is corrected that may speed things.  I am wondering what 
> others have done/seen with this and whether upgrading to 4.4.0 would do me 
> good.  I am thinking it would as many things appear to fixed around the 
> issues I am seeing.  Thanks in advance,
>
> Mike
>

-- 
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/d2aad3a9-40d2-4d79-bb46-32e2ffe357e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

[Peter Krawetzky]

Hi Mike, glad to hear I'm not the only one with the headaches :)

We are planning on upgrading everything across the board from puppet 
server, puppet agent and puppet db.  At least now I can get back to 
planning that!

Our catalog/resource duplication is zero after about 5 hours of running.  I 
need to look at this as well but suspect each agent run has different data 
or catalog compile.  I need to look into those more just like you do when 
time permits.  Command queue has peeked at 5 max and command processing/sec 
is 1.93.

Let me know if you have any questions.

On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote:
>
> Last Sunday we hit a wall on our 3.0.2 puppetdb server.  The cpu spiked 
> and the KahaDB logs started to grow eventually almost filling a 
> filesystem.  I stopped the service, removed the mq directory per a 
> troubleshooting guide, and restarted.  After several minutes the same 
> symptoms began again and I have not been able to come up with a puppetdb or 
> postgresql config to fix this.
>
> We tried turning off storeconfig in the puppet.conf file on our puppet 
> master servers but that doesn't appear to have resolved the problem.  I 
> also can't find a good explanation as to what this parameter really does or 
> does not do even in the puppet server documentation.  Anyone have a better 
> insight into this?
>
> Also is there a way to just turn off puppetdb?
>
> I've attached a file that is a snapshot of the puppetdb dashboard.
>
> Anyone experience anything like this?
>

-- 
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/1b82f569-81b0-4bbf-8f49-f2e94a799e21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Compare node fact runs

[Peter Krawetzky]

I'm seeing a lot of replace facts in the puppetdb server log.  I googled 
but can't find anything solid.

Is there a way to compare facts for a node between runs?  Our agents run 
hourly.  We are using open source PuppetDB 3.0.2.

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/6d0194fd-6fe9-4e2a-9cce-28ac487e8540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

[Peter Krawetzky]

Well after several attempts at tuning the DB config and puppetdb config, we 
had to drop the postgresql database and recreate it then allowing puppetdb 
to create the required tables, indexes, etc.  Now the command queue is 
going between zero and four, processed tens of thousands of queue commands 
(since restarting at 10:15am) and the cpu load on the server is next to 
nothing.

My guess is the database was corrupt somehow with all of the deletes from 
the KahaDB directory plus trying to remove a huge amount of facts.  I think 
puppet needs to provide some type of DB reset process without have to 
drop/create the DB.

On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote:
>
> Last Sunday we hit a wall on our 3.0.2 puppetdb server.  The cpu spiked 
> and the KahaDB logs started to grow eventually almost filling a 
> filesystem.  I stopped the service, removed the mq directory per a 
> troubleshooting guide, and restarted.  After several minutes the same 
> symptoms began again and I have not been able to come up with a puppetdb or 
> postgresql config to fix this.
>
> We tried turning off storeconfig in the puppet.conf file on our puppet 
> master servers but that doesn't appear to have resolved the problem.  I 
> also can't find a good explanation as to what this parameter really does or 
> does not do even in the puppet server documentation.  Anyone have a better 
> insight into this?
>
> Also is there a way to just turn off puppetdb?
>
> I've attached a file that is a snapshot of the puppetdb dashboard.
>
> Anyone experience anything like this?
>

-- 
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/27a1ac7d-d024-4489-bac8-77f41080d80f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

[Peter Krawetzky]

Chris that is this my take on historical data as well.  We have processes 
that export the data to a data warehouse for consumption by other apps. 
 Missing some won't kill that process, like the data never existed.

On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote:
>
> Last Sunday we hit a wall on our 3.0.2 puppetdb server.  The cpu spiked 
> and the KahaDB logs started to grow eventually almost filling a 
> filesystem.  I stopped the service, removed the mq directory per a 
> troubleshooting guide, and restarted.  After several minutes the same 
> symptoms began again and I have not been able to come up with a puppetdb or 
> postgresql config to fix this.
>
> We tried turning off storeconfig in the puppet.conf file on our puppet 
> master servers but that doesn't appear to have resolved the problem.  I 
> also can't find a good explanation as to what this parameter really does or 
> does not do even in the puppet server documentation.  Anyone have a better 
> insight into this?
>
> Also is there a way to just turn off puppetdb?
>
> I've attached a file that is a snapshot of the puppetdb dashboard.
>
> Anyone experience anything like this?
>

-- 
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/04350a71-df08-4745-b3fc-1578359c92bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

[Peter Krawetzky]

So after a change from the module owner who's fact's were very very large, 
the java CPU has been reduced significantly and running much better. 
 However, now that the facts have changed for every single node, the DB is 
doing a significant amount of work to clean things up.  And the KahaDB 
queue is still growing out of control. 

At this point it might be a better option to stop the puppetdb server, 
shutdown postgresql, delete the data directory (after copying pg_hba.conf 
and postgresql.conf to /tmp), init a new db, copy those 2 files from /tmp 
back to their original spot, start postgresql and start puppetdb allowing 
it to create everything it needs from scratch.  Any opinions?

On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote:
>
> Last Sunday we hit a wall on our 3.0.2 puppetdb server.  The cpu spiked 
> and the KahaDB logs started to grow eventually almost filling a 
> filesystem.  I stopped the service, removed the mq directory per a 
> troubleshooting guide, and restarted.  After several minutes the same 
> symptoms began again and I have not been able to come up with a puppetdb or 
> postgresql config to fix this.
>
> We tried turning off storeconfig in the puppet.conf file on our puppet 
> master servers but that doesn't appear to have resolved the problem.  I 
> also can't find a good explanation as to what this parameter really does or 
> does not do even in the puppet server documentation.  Anyone have a better 
> insight into this?
>
> Also is there a way to just turn off puppetdb?
>
> I've attached a file that is a snapshot of the puppetdb dashboard.
>
> Anyone experience anything like this?
>

-- 
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/42d78acf-727e-406f-a2c1-f6253121991b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet agent running on same host as puppet server, possible cert issues

[Peter Faller]

Is the puppet agent running as the same user when run as a daemon and when 
run via 'puppet agent' from the command line? I've seen that make a 
difference.

On Monday, 3 July 2017 15:49:06 UTC+2, aaron@gmail.com wrote:
>
>
>>>
>>>

-- 
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/462ba21b-830a-4fad-a542-11423a09c221%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: How to get remote node ip

[Peter Faller]

If you know what physical interface that address is on, you can use 
'ipaddress_ens33' for example:

# facter --puppet | fgrep interface
interfaces => ens32,ens33,lo
# facter --puppet | fgrep ip
ipaddress => 192.168.51.106
ipaddress_ens32 => 192.168.51.106
ipaddress_ens33 => 192.168.53.106
ipaddress_lo => 127.0.0.1


On Tuesday, 4 July 2017 11:21:33 UTC+2, Александр Подолин wrote:
>
>
>

-- 
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/660bc19f-996d-4b30-a81c-14db75992b15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

[Peter Krawetzky]

What is the actual definition of store_usage?  It's not very specific. 
 Does it limit the number of KahaDB logs?  If so what happens when that 
limit is reached?

On Wednesday, June 28, 2017 at 12:25:57 PM UTC-4, Peter Krawetzky wrote:
>
> Last Sunday we hit a wall on our 3.0.2 puppetdb server.  The cpu spiked 
> and the KahaDB logs started to grow eventually almost filling a 
> filesystem.  I stopped the service, removed the mq directory per a 
> troubleshooting guide, and restarted.  After several minutes the same 
> symptoms began again and I have not been able to come up with a puppetdb or 
> postgresql config to fix this.
>
> We tried turning off storeconfig in the puppet.conf file on our puppet 
> master servers but that doesn't appear to have resolved the problem.  I 
> also can't find a good explanation as to what this parameter really does or 
> does not do even in the puppet server documentation.  Anyone have a better 
> insight into this?
>
> Also is there a way to just turn off puppetdb?
>
> I've attached a file that is a snapshot of the puppetdb dashboard.
>
> Anyone experience anything like this?
>

-- 
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/eab67fff-269e-40fe-80c6-5c7a8f135387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.