Re: [Puppet Users] Help with hiera.yaml config
I've tried that also but then it's removing both entries. Op dinsdag 11 augustus 2015 03:28:12 UTC+2 schreef gregory...@calorieking.com: Hi Patrick, On 10/08/15 17:10, Patrick G. wrote: parameters: sudoroles: 'root_users' sudoroles: 'dba_users' That reads to me like you've overwritten the first sudoroles value with the second entry. If you want both, it would need to be e.g. an array: parameters: sudoroles: - 'root_users' - 'dba_users' ... with relevant logic in the module to handle an array. HTH, Greg. -- 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/218057c7-c6fc-438e-9bee-b8931afd8223%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] PuppetDB remote connection not working with CURL but working with openssl
Hi,
I am trying to query the puppetdb from a remote server using curl and
https without success.
I have already generated the certificates and move them the remote server.
Using openssl all works ok
First I launch the following command:
openssl s_client -connect puppetdb:8081 -CAfile ca.pem -cert
pentahotest.pem.cer -key pentahotest.pem.priv
Once the connection is stablished I send the url to get the results:
get /v3/nodes
[ {
name : server1,
deactivated : null,
catalog_timestamp : 2015-08-13T09:12:44.087Z,
facts_timestamp : 2015-08-13T09:12:35.127Z,
report_timestamp : 2015-08-13T09:13:10.401Z
}
[...]
So certificates are working ok. But If I use CURL with same
certificates it doesn't works
$ curl -vvv -sfG 'https://puppetdb:8081/v3/nodes' --cacert ca_crt.pem
--cert pentahotest.pem.cer --key pentahotest.pem.priv
* STATE: INIT = CONNECT handle 0x600057080; line 1075 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* Trying X.X.X.X...
* STATE: CONNECT = WAITCONNECT handle 0x600057080; line 1128 (connection #0)
* Connected to puppetdb (X.X.X.X) port 8081 (#0)
* STATE: WAITCONNECT = SENDPROTOCONNECT handle 0x600057080; line 1225
(connection #0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* error setting certificate verify locations:
CAfile: ca_crt.pem
CApath: none
* STATE: SENDPROTOCONNECT = PROTOCONNECT handle 0x600057080; line
1239 (connection #0)
* Expire cleared
* Curl_done
* Closing connection 0
* The cache now contains 0 members
Any idea what am I doing wrong?
Best regards
--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
--
--
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/CABS%3Dy9tJ5321SNXJKTPgHY-5T4vGj19HNhp-_MPfM7QA1njbRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] get data from yaml in subdirs
Hi,
Can someone please explain something.
I have a hiera.yaml:
---
:backends:
- yaml
:yaml:
:datadir: /etc/puppet/hieradata
:hierarchy:
- usergroups/%{::usersgroups}
- global
global.yaml contains:
---
test: Test_output
When I do a:
hiera -c /etc/puppet/hiera.yaml test
I'll get:
Test_output
but i want this global.yaml in /etc/puppet/hieradata/usergroups
But how do call this information from a subdir?
regards, patrick.
--
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/49bc3764-3ec8-4fbf-aea5-ace988a456dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Help with hiera.yaml config
What I have is:
---
:backends:
- yaml
:yaml:
:datadir: /etc/puppet/hieradata
:hierarchy:
- nodes/%{::fqdn}
- usergroups/%{usergroups}
---
classes:
- colorprompt
- ntp
- motd
- ssh
- sudodba
- sudoroot
colorprompt::server_color: 'blue'
parameters:
usergroups:
- 'root'
- 'admiam'
- 'oracle'
This works:
hiera -c /etc/puppet/hiera.yaml -d ssh::keys usergroups=oracle
But it won't put al the usergroups on this server.
Op maandag 10 augustus 2015 11:10:44 UTC+2 schreef Patrick G.:
Hi,
I have the following config.
:backends:
- yaml
:yaml:
:datadir: /etc/puppet/hieradata
:hierarchy:
- nodes/%{::fqdn}
- sudoroles/%{::sudoroles}
- common
In sudorules I have twho files with root users en dba users.
On a server I want both root users and dba users and on the other server
only the root user.
In enc/nodes/server1 i have:
---
classes:
- sudoroles
parameters:
sudoroles: 'root_users'
sudoroles: 'dba_users'
But only dba_users are created and the root_users removed.
Can someone please help how to do this?
Regards, Patrick.
Op dinsdag 11 augustus 2015 03:28:12 UTC+2 schreef
gregory...@calorieking.com:
Hi Patrick,
On 10/08/15 17:10, Patrick G. wrote:
parameters:
sudoroles: 'root_users'
sudoroles: 'dba_users'
That reads to me like you've overwritten the first sudoroles value with
the second entry. If you want both, it would need to be e.g. an array:
parameters:
sudoroles:
- 'root_users'
- 'dba_users'
... with relevant logic in the module to handle an array.
HTH,
Greg.
--
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/f7f00663-174f-4cb7-86c2-0272b4b6dd61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] keep changing owner
Hi, When running puppet agent -t I get Notice: /File[/var/lib/puppet/lib]/owner: owner changed 'puppet' to 'root' Notice: /File[/var/lib/puppet/lib]/group: group changed 'puppet' to 'root' And then Notice: /Stage[main]/My_fw/File[/var/lib/puppet/lib]/owner: owner changed 'root' to 'puppet' Notice: /Stage[main]/My_fw/File[/var/lib/puppet/lib]/group: group changed 'root' to 'puppet' For a lot of files. Why? Regards, Patrick. -- 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/1af6a1e5-4125-457c-a0ec-5b0a139042df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Help with hiera.yaml config
What I have is:
---
:backends:
- yaml
:yaml:
:datadir: /etc/puppet/hieradata
:hierarchy:
- nodes/%{::fqdn}
- usergroups/%{usergroups}
---
classes:
- colorprompt
- ntp
- motd
- ssh
- sudodba
- sudoroot
colorprompt::server_color: 'blue'
parameters:
usergroups:
- 'root'
- 'admiam'
- 'oracle'
This works:
hiera -c /etc/puppet/hiera.yaml -d ssh::keys usergroups=oracle
But it won't put al the usergroups on this server.
Op maandag 10 augustus 2015 11:10:44 UTC+2 schreef Patrick G.:
Hi,
I have the following config.
:backends:
- yaml
:yaml:
:datadir: /etc/puppet/hieradata
:hierarchy:
- nodes/%{::fqdn}
- sudoroles/%{::sudoroles}
- common
In sudorules I have twho files with root users en dba users.
On a server I want both root users and dba users and on the other server
only the root user.
In enc/nodes/server1 i have:
---
classes:
- sudoroles
parameters:
sudoroles: 'root_users'
sudoroles: 'dba_users'
But only dba_users are created and the root_users removed.
Can someone please help how to do this?
Regards, Patrick.
--
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/a0863954-80a0-4292-91f7-a351d427ab87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: PuppetDB remote connection not working with CURL but working with openssl
The problem was between the seat and the keyboard :P
I was using different ca names (ca_crt.pem != ca.pem)
Now it works perfectly
Best regard
--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
--
2015-08-13 11:43 GMT+02:00 Juan Sierra Pons j...@elsotanillo.net:
Hi,
I am trying to query the puppetdb from a remote server using curl and
https without success.
I have already generated the certificates and move them the remote server.
Using openssl all works ok
First I launch the following command:
openssl s_client -connect puppetdb:8081 -CAfile ca.pem -cert
pentahotest.pem.cer -key pentahotest.pem.priv
Once the connection is stablished I send the url to get the results:
get /v3/nodes
[ {
name : server1,
deactivated : null,
catalog_timestamp : 2015-08-13T09:12:44.087Z,
facts_timestamp : 2015-08-13T09:12:35.127Z,
report_timestamp : 2015-08-13T09:13:10.401Z
}
[...]
So certificates are working ok. But If I use CURL with same
certificates it doesn't works
$ curl -vvv -sfG 'https://puppetdb:8081/v3/nodes' --cacert ca_crt.pem
--cert pentahotest.pem.cer --key pentahotest.pem.priv
* STATE: INIT = CONNECT handle 0x600057080; line 1075 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* Trying X.X.X.X...
* STATE: CONNECT = WAITCONNECT handle 0x600057080; line 1128 (connection #0)
* Connected to puppetdb (X.X.X.X) port 8081 (#0)
* STATE: WAITCONNECT = SENDPROTOCONNECT handle 0x600057080; line 1225
(connection #0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* error setting certificate verify locations:
CAfile: ca_crt.pem
CApath: none
* STATE: SENDPROTOCONNECT = PROTOCONNECT handle 0x600057080; line
1239 (connection #0)
* Expire cleared
* Curl_done
* Closing connection 0
* The cache now contains 0 members
Any idea what am I doing wrong?
Best regards
--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE
--
--
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/CABS%3Dy9vJYN4rQP8b%2Bzsrn6jx8Cp8PJ7uM2p_9KUmntY5_Eg4vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Help on puppet ERB template
On Wednesday, August 12, 2015 at 8:52:50 AM UTC-5, b.gold...@gmail.com wrote: Hi Guys I am new to puppet and ruby. I am working on some erb template for ldap. Following is sample code % if TCPSocket.new(host1, 636) and TCPSocket.new(host2, 636) % host port 636 tls_checkpeer yes % else -% host port 389 tls_checkpeer no % end % Above works if 636 is open but if its not then it never goes to else but raise exception of connection refused and eventually puppet fails. I tried catching exception in erb template but it didnt work. Possible to catch exceptions like below ? I want to exit it if any exception is raised. rescue Errno:: ECONNREFUSED = e First of all, I urge you to choose an altogether different way to determine which alternative you want your template to exercise. It is usually better in Puppet to choose configuration details based on static information (recorded in an Hiera data store, for example) or semi-static information (e.g. based on resources exported during the process of building other nodes' catalogs). There is a range, but ephemeral data such as whether the master can establish a TCP connection to a particular host at a particular time are a particularly poor basis for such choices. If you insist on proceeding in that direction, however, then you need to recognize that when TCPSocket.new() fails, it throws an exception rather than returning a value that evaluates to false. If you want processing to continue within your template, then you need it to catch that exception. That would look something like this: % begin TCPSocket.new(host1, 636) and TCPSocket.new(host2, 636) % host port 636 tls_checkpeer yes % rescue -% host port 389 tls_checkpeer no % end % Overall, always remember that ERB is just a somewhat unusual way to write ordinary Ruby code. It's expressed inside out, but once you learn to see through that to the all-Ruby code it represents, you can rely on your Ruby knowledge (or someone else's) to understand how to create, interpret, and use ERB templates. 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/7655cf9e-07cf-45d4-b8b0-b18b6b7b61fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: [Puppet-dev] Debian Testing and Debian Stable leaving apt.puppetlabs.com
On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone meli...@puppetlabs.com wrote: In an effort to reduce duplication and confusion in the packages we provide, we will no longer be providing packages for Debian Testing or Debian Stable. We want to ensure we deliver tested and reliable packages, which includes deliberately adding new platforms that have been vetted. This change is part of an effort to ensure that is always the case with the packages we make available. To clarify, because this has confused other people too: does this mean that you won’t be able to run Puppet from an official package on Debian Stable? Or is there another repo that can be added, that’s just not specific to Debian Testing/Stable? Thanks, Daniel -- 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/CAPNukCk5jhKJcy%2B5OAUN57xevu8FbX4iBGVkip-ae1Qy7-YN6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: [Puppet-dev] Debian Testing and Debian Stable leaving apt.puppetlabs.com
On Thu, Aug 13, 2015 at 11:12 AM, Daniel Parks d...@puppetlabs.com wrote: On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone meli...@puppetlabs.com wrote: In an effort to reduce duplication and confusion in the packages we provide, we will no longer be providing packages for Debian Testing or Debian Stable. We want to ensure we deliver tested and reliable packages, which includes deliberately adding new platforms that have been vetted. This change is part of an effort to ensure that is always the case with the packages we make available. To clarify, because this has confused other people too: does this mean that you won’t be able to run Puppet from an official package on Debian Stable? Debian Stable now corresponds to Debian Jessie. We currently have puppet-agent packages available for Debian Jessie, and puppetserver packages are in the works. Those can/will be made available in the PC1 repos at http://apt.puppetlabs.com/pool/jessie/PC1/ Or is there another repo that can be added, that’s just not specific to Debian Testing/Stable? Thanks, Daniel -- 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/CAPNukCk5jhKJcy%2B5OAUN57xevu8FbX4iBGVkip-ae1Qy7-YN6A%40mail.gmail.com https://groups.google.com/d/msgid/puppet-users/CAPNukCk5jhKJcy%2B5OAUN57xevu8FbX4iBGVkip-ae1Qy7-YN6A%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- 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/CAHEe_kpjoH4QZG%2BJyx5hpA5aKYE%3DzmMNn6Xnbfpfgww2nUFU5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Debian Testing and Debian Stable leaving apt.puppetlabs.com
On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone meli...@puppetlabs.com wrote: In an effort to reduce duplication and confusion in the packages we provide, we will no longer be providing packages for Debian Testing or Debian Stable. We want to ensure we deliver tested and reliable packages, which includes deliberately adding new platforms that have been vetted. This change is part of an effort to ensure that is always the case with the packages we make available. Stable and Testing packages will be removed from our apt repository on Wednesday, September 9th. For clarity, this is only referring to packages built under the stable and testing name spaces. We will continue to support and ship packages associated with current supported Debian codenames (i.e. Debian Wheezy and Debian Jessie). -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- 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/CAHEe_kqaMtof6%3DKGKbtqnnhTdEu5Y_ReTBbMDK_mkn89Xq%3D4xA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] 2015.2 strange message
Spun up a 2015.2 system and every time an agent runs we see Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution. Any ideas ? I saw one bug report at https://github.com/gentoo/puppet-portage/issues/136 saying facter needed to be updated and this was allegedly done in 2015.2, but perhaps not (???) Vagrant box I'm testing on is centos-6.7 fully patched 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/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] 2015.2 strange message
Hi Vince, On Thu, Aug 13, 2015 at 10:21 AM, Vince Skahan vinceska...@gmail.com wrote: Spun up a 2015.2 system and every time an agent runs we see Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution. Any ideas ? I saw one bug report at https://github.com/gentoo/puppet-portage/issues/136 saying facter needed to be updated and this was allegedly done in 2015.2, but perhaps not (???) This was fixed in the puppet-portage module itself, so updating the module to a fixed version or porting the fix to the fact file (simply delete the require 'facter/util/resolution' line) should solve the problem with Facter 3. This particular fix is also backwards compatible with 2.x, as 2.x also required this file before resolving any custom facts. If memory serves, I searched through the Forge for references in custom facts depending on the Facter 2.x implementation's file structure and found only this one. Therefore I didn't end up adding the workaround to Facter itself to support requiring parts of 2.x Facter beyond simply `require 'facter'` (which itself is also unnecessary, but was more frequently done). We could revisit fixing this in Facter itself (basically manipulating the load path to fake the load of 'facter/util/resolution') if it proves to be a more widespread problem affecting other modules. Vagrant box I'm testing on is centos-6.7 fully patched 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/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- -- Peter Huene Software Engineer, Puppet Labs Puppet Open Source Team --- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9! -- 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/CACZQQfO%2B0tnOaFxR6W5L%3DZVaSeF2OdjutH%2B9w%3DPUi4xeJDjcDA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Mac Warranty Fact
I stumbled on a Facter fact that was written by Gary Larizza back in 2011 (https://github.com/glarizza/puppetrepo/blob/master/modules/custom/lib/facter/warranty.rb) that checks the warranty on Mac computers. The warranty site it checks has changed significantly since then. Is anyone else using a variation of this fact or have a better Facter fact they are using in their 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/5080d6fe-e37b-4316-8c24-736555d4346f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: PuppetDB 2.3.7 is available
PuppetDB 2.3.7 August 13, 2015 PuppetDB 2.3.7 Downloads Available in native package format in the release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories Binary tarball: http://downloads.puppetlabs.com/puppetdb/ Source: http://github.com/puppetlabs/puppetdb Please report feedback via the Puppet Labs tickets site, using an affected PuppetDB version of 2.3.7: https://tickets.puppetlabs.com/browse/PDB Documentation: http://docs.puppetlabs.com/puppetdb/2.3/ Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb PuppetDB 2.3.7 Release Notes PuppetDB 2.3.7 is a backwards-compatible bugfix release that applies the default max-frame-size setting to affect ActiveMQ consumer threads in addition to producers (which were already affected). This could cause issues with submission of extremely large commands. The max-frame-size setting is currently not configurable due to a separate bug (https://tickets.puppetlabs.com/browse/PDB-1909), but the default should be sufficient in all cases but the most extreme. For more information and upgrade advice, consult the detailed release notes here: https://docs.puppetlabs.com/puppetdb/2.3/release_notes.html Contributors Andrew Roetker, Russell Mull -- 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/CAJDiH3GWXKOZ3xNcSuJ_8za5tLHEdK9R5euKrSSG_-6NRsea8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] 2015.2 strange message
I'm sorry but you're going to need to reparse that one into English. You want me to check for what (where?) and change what (where?) ? On Thursday, August 13, 2015 at 11:44:25 AM UTC-7, Peter Huene wrote: On Thu, Aug 13, 2015 at 10:21 AM, Vince Skahan vince...@gmail.com javascript: wrote: Spun up a 2015.2 system and every time an agent runs we see Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution. Any ideas ? I saw one bug report at https://github.com/gentoo/puppet-portage/issues/136 saying facter needed to be updated and this was allegedly done in 2015.2, but perhaps not (???) This was fixed in the puppet-portage module itself, so updating the module to a fixed version or porting the fix to the fact file (simply delete the require 'facter/util/resolution' line) should solve the problem with Facter 3. This particular fix is also backwards compatible with 2.x, as 2.x also required this file before resolving any custom facts. If memory serves, I searched through the Forge for references in custom facts depending on the Facter 2.x implementation's file structure and found only this one. Therefore I didn't end up adding the workaround to Facter itself to support requiring parts of 2.x Facter beyond simply `require 'facter'` (which itself is also unnecessary, but was more frequently done). We could revisit fixing this in Facter itself (basically manipulating the load path to fake the load of 'facter/util/resolution') if it proves to be a more widespread problem affecting other modules. Vagrant box I'm testing on is centos-6.7 fully patched 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...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- -- Peter Huene Software Engineer, Puppet Labs Puppet Open Source Team --- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9! -- 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/f1afa917-2cd3-4955-8056-5c47feba170f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Debian Testing and Debian Stable leaving apt.puppetlabs.com
In an effort to reduce duplication and confusion in the packages we provide, we will no longer be providing packages for Debian Testing or Debian Stable. We want to ensure we deliver tested and reliable packages, which includes deliberately adding new platforms that have been vetted. This change is part of an effort to ensure that is always the case with the packages we make available. Stable and Testing packages will be removed from our apt repository on Wednesday, September 9th. -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- 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/CAHEe_kqqW%2BMc%2BRstxB0yLchLBWZQXWuOnTM_UKDzS1o47DsB0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
