Re: [Puppet Users] Re: hiera deep hash merges broken
On Wed, Feb 15, 2017 at 06:47 Francois Lafont < francois.lafont.1...@gmail.com> wrote: > Oops, I have forgotten to say this: > > On 02/14/2017 08:51 PM, Daniel Urist wrote: > > > Just found this issue, which seems to describe what's going on: > > https://github.com/TomPoulton/hiera-eyaml/issues/222 > > So eyaml is broken wrt hash merges? Are there any workarounds available? > > Currently, the problem happens with puppet-agent version 1.9.x. > No problem with the version 1.8.3. So it could be a temporarily > workaround. Thanks all for the reports. A fix is in progress / en route, trackable via https://tickets.puppetlabs.com/browse/PUP-7215 > > François Lafont > > -- > 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/c473132b-b49f-2081-44dd-26fecc216b7f%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Moses Mendoza Puppet -- 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%2B421WYfqwb4EcotfiGJidY0TvurApQtQCuRRK%3DPDAzy5DS2gA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet and cfpropertylist
Hi Luke - What version of puppet-agent is running on the host you have installed puppetserver on? Can you link a gist of the output of running `sudo /opt/puppetlabs/puppet/bin/puppet agent -t --trace --debug` on the puppet server host (with sensitive info, if any, redacted)? On Thu, Dec 1, 2016 at 9:23 PM, Luke Tinker wrote: > I am getting the following error in multiple places on my puppet master > server after moving to puppet server 2.7.1 after running on the old 3.8.7 > build of puppet, > > when launching the server > 2016-12-02 15:37:44,863 INFO [clojure-agent-send-pool-0] [puppetserver] > Puppet Puppet settings initialized; run mode: master > Failed to load feature test for cfpropertylist: no such file to load -- > CFPropertyList > 2016-12-02 15:37:45,295 INFO [clojure-agent-send-pool-0] > [p.s.j.i.jruby-agents] Finished creating JRubyInstance 2 of 2 > > > when running "sudo /opt/puppetlabs/puppet/bin/puppet master download" > Failed to load feature test for cfpropertylist: cannot load such file -- > CFPropertyList > > when running " sudo /opt/puppetlabs/puppet/bin/puppet agent -t --onetime" > > Failed to load feature test for cfpropertylist: cannot load such file -- > CFPropertyList > Info: Using configured environment 'production' > Info: Retrieving pluginfacts > Info: Retrieving plugin > Failed to load feature test for cfpropertylist: cannot load such file -- > CFPropertyList > Info: Loading facts > Info: Caching catalog for moedevsrv09.uds.anu.edu.au > Info: Applying configuration version '1480655880' > Notice: Applied catalog in 0.11 seconds > > the error: Failed to load feature test for cfpropertylist: cannot load such > file -- CFPropertyList > seems to be coming up everywhere on the server, > also modules that actually use the cfpropertylist of course do not work for > clients. > > I have tried installing the cfpropertylist ruby gem in all sorts of places, > even embedded it in too a module, > > I am starting to get to the point where i just have no idea what else i can > do and wanted to check with the community, > any recommendations or suggestions> > > -- > 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/2b5c62d9-46fb-4d83-b90d-d91af76e7940%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Moses Mendoza Puppet -- 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%2B421WY-UquO1%3DhvbaYM8N4vQvh7Px%3D40enhf%3D7MePLUgcU7mA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Puppet Agent 1.8.0 is available
Thanks for reporting this Michael. Another user has reported the same in https://tickets.puppetlabs.com/browse/PUP-6861 - we'll track the issue via this ticket. On Wed, Nov 2, 2016 at 6:18 AM, Michael Watters wrote: > There seems to be a bug in the mount provider with the new puppet-agent > 1.8 package. I have a node that is reporting changed file system > options every time that puppet runs although nothing is actually > changing. I downgraded back to puppet-agent 1.7.1 and this behavior > goes away. > > >Notice: /Stage[main]/Mount[/srv/git_home]/options: options changed > 'bind' to 'bind' > > My cifs mounts are also reporting "changed" file system options as shown > below. > > > Mount[/srv/mas-cad55-volumes]/options: options changed > 'credentials=/etc/tc-credentials,dir_mode=0555' to > 'credentials=/etc/tc-credentials,dir_mode=0555' > > As you can see these are the exact same string. > > > > On Tuesday, November 1, 2016 at 9:29:23 PM UTC-4, Geoff Nichols wrote: >> >> I’m excited to announce a new backwards-compatible feature release of >> Puppet Agent. Puppet Agent 1.8.0 contains several updated component >> versions, including new feature releases of Puppet and Facter. >> >> * Puppet 4.8.0 - This release includes several improvements to the type >> system and updates puppet module tool to use "forgeapi.puppet.com" >> (instead of "forgeapi.puppetlabs.com"). >> >> * Facter 3.5.0 - New feature release allowing settings for configuring >> external and custom fact directories, setting command line options, and >> blocking facts - loaded by default from /etc/puppetlabs/facter/facter. >> conf. >> >> This release also adds support for macOS Sierra and Windows Server 2016. >> >> Release notes for each of these are linked from the main puppet-agent >> note: https://docs.puppet.com/puppet/4.8/reference/release_notes_ >> agent.html >> >> For information on upcoming platform end-of-life (EOL) for Puppet Agent, >> please see our Platform Support Lifecycle page: >> https://puppet.com/content/platform-support-lifecycle >> >> Community shout-out to Clay Caviness for several contributions to this >> release - including a fix for ‘tidy’ and additional fixes for Mac OS X. >> >> >> -- >> Geoff Nichols >> Puppet Ecosystem - Agent and Platform Team >> > -- > 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/0e45a4d0-5b87-4d5d-9a23-0530f7b57bbf%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/0e45a4d0-5b87-4d5d-9a23-0530f7b57bbf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Moses Mendoza Puppet -- 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%2B421WbfcG9Y%3DVLfhm30-%2Bb70hNksbhuG7kB_T6JuZ3Nf0fCqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] facter ignores all executable facts with exception of ruby scripts
On Wed, Sep 14, 2016 at 6:31 AM, 'Peter Krauspe' via Puppet Users wrote: > Hi , > > I'm using facter puppet 3.8 7 with factor 2.4.6 on CentOS 7 > > According to puppet/facter docu it's possible to add executable custom facts > using ruby/shell/python scripts and just *.txt files. > > I tried the following: > > /ruby.rb > /python.py > /shell.sh > /file.txt > > The contens is quite simple > The ruby script runs an external shell command and adds a fact asigning the > output of the shell command > > The shell and python Scripts return some key=value Strings . e.g > > key1=val1 > key2=val2 > > The text file just consists of the above lines > > I tried for example > > export FACTERLIB= > facter key1 > > All methods are described in the docu, but everything fails. Only the ruby > script > leads to an output > > facter --debug option gave an error message in ALL methods, even in case of > the ruby facts (but here after the error message the output appears) > > What's going wrong here ? > > -- > 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/03b01e8c-b85f-404e-9e27-7460725aa7c2%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. Hi Peter - Facter only loads "custom facts" (facts in the standard facter format in ruby *.rb files) in directories specified by FACTERLIB[1]. When using "external facts" (facts derived from arbitrary executable files returning key/value pairs on stdout) the files containing the facts have to reside in a directory supplied as the value to the `--external-dir` flag to facter, ie `facter key1 --external-dir https://docs.puppet.com/facter/3.4/custom_facts.html#using-the-facterlib-environment-variable [2] https://docs.puppet.com/facter/3.4/custom_facts.html#fact-locations -- Moses Mendoza Puppet Labs -- 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%2B421WbTsTHha%2BpC98_U%3DH0%3Djmko-xZZKVERefcTZHhYSo4vQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Exec Command
On Thu, Sep 1, 2016 at 3:00 AM, megha sharma wrote:
> Hello,
>
> Where can I find the output logs after running exec command on windows
> puppet agent.
>
> Thanks,
> Megha
>
> --
> 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/752a48c3-5c8a-494e-8111-51fb4f9a5500%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Hi Megha,
The output should be recorded as an event in Event Viewer (in Windows
Logs => Application). You'll need to specify `logoutput => true` in
your exec resource to actually log the output though, ie:
For example with:
exec { 'my command' :
command => 'Write-Host "hello world"',
provider=> 'powershell',
logoutput => true,
}
--
Moses Mendoza
Puppet Labs
--
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%2B421WZbtHL%3Dftmskg4D0hn%2Bi%2BQxFKZe_ym9pKRKrZE8adDD7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] New puppet-security-announce list
We have created a new low-volume read-only mailing list for security-related announcements: puppet-security-announce. This list will contain only announcements of Puppet Labs software releases that address security vulnerabilities and other security-related information. This includes information regarding both our open-source and commercial software. If you would like to subscribe, visit https://groups.google.com/group/puppet-security-announce. Thanks, -- Moses Mendoza Puppet Labs Join us at PuppetConf 2015, October 5-9 in Portland, OR - http://2015.puppetconf.com Register early to save 40%! -- 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%2B421WYzHf5yz_wYWB%3Dn4JseWfMQofNbydZPz12yW_YshJtTrA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Enterprise 2 Series End of Life
All, Puppet Enterprise 2.8 is now end of life. This brings to a close the last chapter of the Puppet Enterprise 2 series, as previously communicated in the Puppet Enterprise Lifecycle[1]. Puppet Enterprise 2.0 was released on November 16, 2011. Since then, we have added major capabilities, expanded platform support, and continually improved the lives of sysadmins by giving them more powerful - and delightful - tools to manage infrastructure. The Puppet Enterprise 3 series started with Puppet Enterprise 3.0 on June 25, 2013. The latest release of Puppet Enterprise is 3.3.2. With Puppet Enterprise 2.8 reaching end of life, we strongly encourage all customers to upgrade to Puppet Enterprise 3.3.2. Please reach out to the Puppet Labs Support Team (supp...@puppetlabs.com) with any questions about the upgrade experience. Thank you, -- Moses Mendoza Puppet Labs [1] PE Lifecycle: http://puppetlabs.com/misc/puppet-enterprise-lifecycle Get PE: http://puppetlabs.com/download-puppet-enterprise-expand How to upgrade: https://docs.puppetlabs.com/pe/latest/install_upgrading.html Customer Support Portal: https://support.puppetlabs.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%2B421WZ%3DQzKGhUJYR5FmDzdPTh3%2BMp88OsxSbs2F5Emuk4KjsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: appdmg and pkgdmg providers download packages insecurely?
Hi Jack, Thanks for pointing this out. We'll look into this asap. Moses On Jun 25, 2014 11:42 AM, "Jack Singleton" wrote: > > Lines in code that are hard coded to use the -k flag: > > https://github.com/puppetlabs/puppet/blob/f1e9a7cb00a3ec01d938cd5c5b1406a82b63d5e7/lib/puppet/provider/package/appdmg.rb#L63 > > https://github.com/puppetlabs/puppet/blob/f1e9a7cb00a3ec01d938cd5c5b1406a82b63d5e7/lib/puppet/provider/package/pkgdmg.rb#L84 > > > On Wednesday, June 25, 2014 12:02:51 AM UTC-7, Jack Singleton wrote: >> >> I just noticed the appdmg and pkgdmg package providers (used on osx) download packages using the curl flag "-k" aka "--insecure" which disables certificate checking. >> >> Is there any reason for this? >> >> At the very least there should be a way to turn insecure mode off. Really it should never be enabled by default. >> >> This introduces a pretty big security vulnerability to workstations set up with Boxen, as remote dmg downloads are encouraged. >> >> Jack > > -- > 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/a1c09705-9ed3-4163-a90a-436f66b07042%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/CA%2B421WYDEkrXp1rTbG%3DE1BCOOQ3PnrzotLsU3Q%2BjD-o7nHZa3A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Community packages : error: rubygem-stomp-1.3.2-1.el5
Hi Dje, Thanks for reporting this. It looks like that package may be signed with the wrong header version. We'll look into it asap. Moses On Jun 26, 2014 6:27 AM, "DjE" wrote: > > Hi, > > We have an issue with this package : error: rubygem-stomp-1.3.2-1.el5: Header V4 RSA/SHA512 signature: BAD, key ID 4bd6ec30 > > Everything works fine with .el6 package. > > Dje > > -- > 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/53AC1811.1010302%40nosbox.net . > 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/CA%2B421WaRZyxfL8LksS0DrJMwTTrrM2cezeWroxs8JvkUiMiZQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Facter 2.0.2 [ Security Release ]
Facter 2.0.2 is a security fix release in the Facter 2 series. This release addresses CVE-2014-3248. It has no other bug fixes or new features. All users of Facter 2.0.1 and earlier are encouraged to update to 2.0.2. ** CVE-2014-3248 ** Arbitrary Code Execution with Required Social Engineering An attacker could convince an administrator to unknowingly create and execute malicious code on platforms with Ruby 1.9.1 and earlier. CVSSv2 Score: 5.2 Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:OF/RC:C Affected Facter versions (ruby 1.9.1 and earlier only): 2.x 1.6.x Fixed Facter versions: 2.0.2 See the Release Notes here: http://docs.puppetlabs.com/facter/2.0/release_notes.html#facter-202 For more information on this vulnerability, please visit https://puppetlabs.com/security/cve/cve-2014-3248 To report issues with the release, file a ticket in the "FACT" project on http://tickets.puppetlabs.com/ and set the "Affects version/s" field to "2.0.2" -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st 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/CA%2B421WYT1owqbQdHQDeSEvb_9o_1zfErQ89%3DOH5qHn%2BtkfquZw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet 3.6.2 [ Security and Bug fix Release ]
Puppet 3.6.2 is a security and bug fix release in the Puppet 3.6 series. This release addresses CVE-2014-3248 and CVE-2014-3250. ** CVE-2014-3248 ** Arbitrary Code Execution with Required Social Engineering An attacker could convince an administrator to unknowingly create and execute malicious code on platforms with Ruby 1.9.1 and earlier. CVSSv2 Score: 5.2 Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:OF/RC:C Affected Puppet versions (ruby 1.9.1 and earlier platforms only): All Fixed Puppet versions: 3.6.2 2.7.26* ** CVE-2014-3250 ** Information Leakage Vulnerability In Apache 2.4, SSLCARevocationCheck directive was added to mod_ssl, which defaults it to none and must be explicitly configured. This setting enables checking of a certificate revocation list. The default Puppet master vhost config shipped with Puppet does not include this setting. If a Puppet master is set up to run with Apache 2.4, and this default vhost configuration file is used, the Puppet master will continue to honor a host's certificate even after it is revoked. CVSSv2 Score: 3.1 Vector: AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:OF/RC:C Affected Puppet versions: All (must be configured as a master behind Apache 2.4 using the default puppet master vhost). Fixed Puppet versions: 3.6.2 For more information on these vulnerabilities, please visit https://puppetlabs.com/security/cve/cve-2014-3248 https://puppetlabs.com/security/cve/cve-2014-3250 ## Bug Fixes Chatty warning/deprecation messages can now be suppressed – as we near the end of the 3.x series, there's going to be a slew of deprecations coming which need to be visible so everyone knows what's going to change, but some messages trigger tons of log spam, so now it's possible to turn them off. Directory environments under webrick now work; they no longer fail with "Attempted to pop, but already at root of the context stack" errors. A memory leak in loading functions was fixed. Community shout-out for this release goes to Joshua Hoblitt for testing the memory leak patch and providing awesome usage graphs (PUP-2692). Please read through the Release Notes for the full list of changes: http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html To install Puppet, follow the Installation Guide:http://docs.puppetlabs.com/guides/install_puppet/pre_install.html To report issues with the release, file a ticket in the “PUP” project on https://tickets.puppetlabs.com/ and set the “Affects version/s” field to "3.6.2”. * The Puppet 2.7.x series is officially end of life, but continues to be maintained by community members. See the release announcement to puppet-announce/puppet-users/puppet-dev regarding Puppet 2.7.26. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st 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/CA%2B421WZmCRv7JGSQdeJ_Spqfn6H87%3DKOMFGt%3DVwRsnQBxcRwfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Mcollective 2.5.2 [ Security Release ]
Mcollective 2.5.2 is a security fix release in the Mcollective 2.5 series. This release addresses CVE-2014-3248. It has no other bug fixes or new features. All users of Mcollective 2.5.1 and earlier are encouraged to update to 2.5.2. ** CVE-2014-3248 ** Arbitrary Code Execution with Required Social Engineering An attacker could convince an administrator to unknowingly create and execute malicious code on platforms with Ruby 1.9.1 and earlier. CVSSv2 Score: 5.2 Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:OF/RC:C Affected Mcollective versions (ruby 1.9.1 and earlier only): All Fixed Mcollective versions: 2.5.2 For more information on this vulnerability, please visit https://puppetlabs.com/security/cve/cve-2014-3248 To report issues with the release, file a ticket in the "MCO" project on http://tickets.puppetlabs.com/ and set the "Affects version/s" field to "2.5.2" -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st 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/CA%2B421WYRKKgsMLpBDnUWKGU0bru8c0%3Dja-X5%3DBovx_pffPaGcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Hiera 1.3.4 [ Security Release ]
Hiera 1.3.4 is a security fix release in the Hiera 1.3 series. This release addresses CVE-2014-3248. It has no other bug fixes or new features. All users of Hiera 1.3.3 and earlier are encouraged to update to 1.3.4. ** CVE-2014-3248 ** Arbitrary Code Execution with Required Social Engineering An attacker could convince an administrator to unknowingly create and execute malicious code on platforms with Ruby 1.9.1 and earlier. CVSSv2 Score: 5.9 Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:U/RC:C Affected Hiera versions (ruby 1.9.1 and earlier platforms only): All Fixed Hiera versions: 1.3.4 See the Release Notes here: http://docs.puppetlabs.com/hiera/1/release_notes.html#hiera-134 To install Hiera, follow the installation guide: http://docs.puppetlabs.com/hiera/1/installing.html For more information on this vulnerability, please visit https://puppetlabs.com/security/cve/cve-2014-3248 To report issues with the release, file a ticket in the "HI" project on http://tickets.puppetlabs.com/ and set the "Affects version/s" field to "1.3.4" -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st 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/CA%2B421WZjNJScw-gMUMH-R4h2wRBJ6r%3DySpLMCHmrBi6RhJFGnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Heartbleed and Puppet-Supported Operating Systems
Hi Darin, Just to clarify - I believe SLES 11 was listed under the section "Operating Systems that are Not Vulnerable." Are you referring to a different document that has been posted? On Thu, Apr 10, 2014 at 3:34 AM, Darin Perusich wrote: > You've listed SLES 11 as vulnerable, it is not. However OpenSUSE 12.3 and > 13.1 are affected and patches have been released. > > http://support.novell.com/security/cve/CVE-2014-0160.html > http://lists.opensuse.org/opensuse-security-announce/2014-04/msg5.html > > On Apr 10, 2014 1:22 AM, "Eric Sorenson" > wrote: >> >> Like you, we are still learning about the full extent of the OpenSSL >> security bug dubbed Heartbleed, and what we need to do to help Puppet users >> remediate the vulnerability. We published step-by-step documentation for >> remediating yesterday >> [http://puppetlabs.com/blog/heartbleed-security-bug-update-puppet-users], >> and we will continue to update you as we learn more and develop new >> resources. >> >> We've finalized a list of vulnerable operating systems supported by Puppet >> Enterprise, noting the versions of OpenSSL they shipped with. If you are >> also running open source Puppet, be aware that the range of operating >> systems you can use is much wider, so not every vulnerable OS is on this >> list. >> >> Keep in mind, regardless of the OS involved, you must check whether you >> are running OpenSSL versions 1.0.1 and 1.0.2 on your systems. Both are >> vulnerable. >> >> Documentation for remediating the Heartbleed issue is linked below the >> lists. For more help, check out the Heartbleed and certificate discussions >> here on the email list >> Vulnerable Operating Systems and their versions of OpenSSL >> Debian Wheezy (stable) >> * OpenSSL 1.0.1e-2+deb7u4 >> Ubuntu 12.04.4 (precise) LTS >> * OpenSSL 1.0.1-4ubuntu5.11 >> RHEL / CentOS / Scientific 6.5 >> * OpenSSL 1.0.1e-15 >> Operating Systems that are Not Vulnerable >> * RHEL / CentOS / OEL / Scientific 6 (other than 6.5) >> * RHEL / CentOS / OEL / Scientific 5 (all versions) >> * RHEL / CentOS 4 >> * SLES 11 >> * AIX 5, 6, 7 >> * Solaris 10, 11 >> * Windows (all) >> * Debian Squeeze (old-stable) >> * Ubuntu 10.04 (Lucid) >> >> Step-by-Step Documentation for Remediating the Vulnerability >> >> Puppet Enterprise 3.x: Regenerating Certs and Security Credentials in >> Split Puppet Enterprise Deployments >> http://docs.puppetlabs.com/pe/3.2/trouble_regenerate_certs_split.html >> >> Puppet Enterprise 3.x: Regenerating Certs and Security Credentials in >> Monolithic Puppet Enterprise Deployments >> >> http://docs.puppetlabs.com/pe/latest/trouble_regenerate_certs_monolithic.html >> >> Puppet Enterprise 2.x: Regenerating Certs and Security Credentials in >> Split Puppet Enterprise Deployments >> http://docs.puppetlabs.com/pe/2.8/trouble_regenerate_certs_split.html >> >> Puppet Enterprise 2.x: Regenerating Certs and Security Credentials in >> Monolithic Puppet Enterprise Deployments >> http://docs.puppetlabs.com/pe/2.8/trouble_regenerate_certs_monolithic.html >> >> Puppet SSL: Regenerating All Certificates in a Puppet Deployment >> >> http://docs.puppetlabs.com/puppet/latest/reference/ssl_regenerate_certificates.html >> >> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 >> puppet platform // coffee // techno // bicycles >> >> -- >> 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/86C75987-61F4-4205-AFF5-5AD25A7946F6%40puppetlabs.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/CADaviKtQGxn41o04-rFdfeU2ewFVAQkNPRrCqmr6OgfSaaTLqw%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/CA%2B421WaYfEyqi2LRRjfcwRxgkZyHc1XKfMWiVUyMTsoC-0fFUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Some of my OS X clients stop checking in with puppet master.
Phil, Kristian, Would you mind posting a gist (any private info retracted of course) of the logs you find this information in? On Thu, Feb 13, 2014 at 5:44 AM, Philip Powell wrote: > I have the same problem. > Looking at the puppet logs on the affected nodes it looks like the puppet > agent will occasionally assume "localhost" as its fqdm and then gives up > when the certs don't match. Maybe it's connected to waking from sleep and > the puppet agent going off before all relevant networky things have been > established. > I too would be majorly chuffed with some kind of fix. > > Phil > > On Wednesday, February 12, 2014 1:24:27 PM UTC+1, Kristian Johannessen > wrote: >> >> I have a strange problem with some of my puppet clients. After a while >> they stop reporting in with the master. If i run the puppet agent manually >> with command (sudo puppet agent -t) everthings looks fine. >> >> The puppet agent is started at boot by the launch daemon that is described >> at puppetlabs.com. I have checked that it's running in the background. So it >> seems to me that there is a issue with the puppet schedule. The issue is not >> relatet to OS, because i have multiple clients running both 10.8 and 10.9 >> that's working... >> >> If anyone have any suggestions how to fix this i would be thrilled.. >> >> Cheers, >> Kristian > > -- > 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/5db0b07e-01c3-406a-bf1e-e6d57502fa08%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14 -- 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%2B421WY62%3DOiqX9JjY6RnByQd%3Dv9Q_AyfJWBQXemTzLmOQDGbw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet post install launchd osx
Hi Rudy,
To uninstall a gem, just do `gem uninstall `, e.g. `gem
uninstall puppet.`.
Just to clarify, the directory you pointed out isn't the gem dir, it's the
Mavericks system ruby site dir.
As you discovered, OSX, the path "/usr/lib/ruby/site_ruby" is actually a
symlink to the directory "/Library/Ruby/Site." This directory is where the
dmg's of puppet, hiera, and facter install to (as shown in your image).
Prior to Puppet 3.4.0 and Facter 1.7.5, the dmgs would install in the
ruby-version-specific subdirectory, "/Library/Ruby/Site/1.8", but we've
moved away from that, as "/Library/Ruby/Site" is in the load path in OSX
versions going awhile back and won't break when ruby versions change.
The gem dir is actually a separate location, where rubygems stores
information about itself, including all of your installed gems. To see the
system gem dir, do `/usr/bin/ruby -e 'puts Gem::dir'`. This should show you
"/Library/Ruby/Gems/2.0.0/", which contains a subdirectory ("gems") with
all of your installed gems. Hope that helps.
Moses
On Tue, Feb 11, 2014 at 9:23 AM, Rudy McComb wrote:
>
> <https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png>
> Moses,
>
> can i rm puppet facter and hiera from the gem dir (usr/lib/ruby/site_ruby)
> w/o breaking puppet dmg installed in correct location?
>
> or is there another remedy you propose?
>
> thanks
>
>
> On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote:
>
>> Hi Rudy,
>>
>> Installing puppet,facter via dmg and also via gem is almost certainly
>> a contributing factor to your issues. The dmg installs to ruby's
>> sitedir (in the load path) and the gem installs to rubygems' gem dir
>> (also in the load path). This means you have two installs of puppet at
>> separate versions in the same ruby load path. This will break things!
>> Charlie explains briefly why this won't work, here:
>> https://projects.puppetlabs.com/issues/19670. You should install from
>> gem or dmg, but not both:) Also, just to be clear, the dmg creates the
>> puppet user, but the gem does not. Finally, facter 1.7.5 was released
>> yesterday, which has mavericks compatibility when installed via dmg.
>> Also, my apologies for calling you 'Ryan'!
>>
>> cheers
>> Moses
>>
>> On Mon, Feb 10, 2014 at 12:14 PM, Rudy McComb
>> wrote:
>> > Hi Moses,
>> >
>> > I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed with
>> the
>> > dmg. I also keep puppet updated
>> > using gem update puppet.
>> >
>> > ill install puppet and facter with the dmg and then gem install puppet
>> so
>> > that it creates the nec users groups etc for puppet.
>> >
>> > I have updated the plist to point to the newer version of ruby since
>> > upgraded macs keep both directories.
>> >
>> >
>> > On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote:
>> >>
>> >> On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb
>> wrote:
>> >> > I'm having a an issue with running puppet as launchd. I'm using this
>> >> > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plistand
>> >> > on
>> >> > some macs it will run and start at reboot and on others it doesnt.
>> >> >
>> >> > According to the logs puppet is exiting with a code of 1. What can
>> i
>> >> > due to
>> >> > ensure that the puppet launchd mod runs uninhibited.
>> >> >
>> >> > http://pastebin.com/raw.php?i=CX56cucf
>> >> >
>> >> > I've also tried using a modified version of this
>> >> >
>> >> >
>> >> > > >> > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
>> >> >
>> >> >
>> >> > EnvironmentVariables
>> >> >
>> >> > PATH
>> >> > /sbin:/usr/sbin:/bin:/usr/bin
>> >> > RUBYLIB
>> >> > /usr/lib/ruby/site_ruby/1.8/
>> >> >
>> >> > Label
>> >> > com.puppetlabs.puppet
>> >> > KeepAlive
>> >> >
>> >> > ProgramArguments
>> >> >
>> >> > /usr/bin/puppet
>
Re: [Puppet Users] RHEL 7 Repository up on yum.puppetlabs.com
On Tue, Feb 11, 2014 at 8:34 AM, Matthias Saou wrote: > On Mon, 10 Feb 2014 11:46:18 -0800 > Melissa Stone wrote: > >> We are pleased to let you know we are currently working on creating >> RHEL 7 packages. We want to do a thorough testing of these packages, >> so we are taking our time with this platform. However, we still want >> to get the packages we do have into your hands. As such, we're going >> to be slowly populating the RHEL 7 repository on yum.puppetlabs.com >> for your consumption. Please, let us know if you run into any issues >> with the available packages by creating an issue at >> tickets.puppetlabs.com. > > I'm not going to create an issue just for that, since it's probably > known, but I couldn't install facter : > > Package facter-1.7.5-1.x86_64.rpm is not signed > > I'll try again it a little while, once puppet is there and once all > repos that are enabled by the release package actually exist :-) > > But it's a good start, much appreciated! > > Matthias Hi Matthias, The package should now be signed. Thanks for reporting that! Moses > > -- > Matthias Saou ██ ██ > ██ ██ > Web: http://matthias.saou.eu/ ██ > Mail/XMPP: matth...@saou.eu ██ >██ > GPG: 4096R/E755CC63██ ██ ██ > 8D91 7E2E F048 9C9C 46AF ██ ██ ██ ██ > 21A9 7A51 7B82 E755 CC63 > > -- > 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/20140211173434.06d5147d%40r2d2.marmotte.net. > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14 -- 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%2B421WZydNGfDD%2BPEp17Z06Nu7Hw86qNxiFO-AUg5nuL0f-F0g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet post install launchd osx
Hi Rudy, Installing puppet,facter via dmg and also via gem is almost certainly a contributing factor to your issues. The dmg installs to ruby's sitedir (in the load path) and the gem installs to rubygems' gem dir (also in the load path). This means you have two installs of puppet at separate versions in the same ruby load path. This will break things! Charlie explains briefly why this won't work, here: https://projects.puppetlabs.com/issues/19670. You should install from gem or dmg, but not both:) Also, just to be clear, the dmg creates the puppet user, but the gem does not. Finally, facter 1.7.5 was released yesterday, which has mavericks compatibility when installed via dmg. Also, my apologies for calling you 'Ryan'! cheers Moses On Mon, Feb 10, 2014 at 12:14 PM, Rudy McComb wrote: > Hi Moses, > > I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed with the > dmg. I also keep puppet updated > using gem update puppet. > > ill install puppet and facter with the dmg and then gem install puppet so > that it creates the nec users groups etc for puppet. > > I have updated the plist to point to the newer version of ruby since > upgraded macs keep both directories. > > > On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote: >> >> On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb wrote: >> > I'm having a an issue with running puppet as launchd. I'm using this >> > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plist and >> > on >> > some macs it will run and start at reboot and on others it doesnt. >> > >> > According to the logs puppet is exiting with a code of 1. What can i >> > due to >> > ensure that the puppet launchd mod runs uninhibited. >> > >> > http://pastebin.com/raw.php?i=CX56cucf >> > >> > I've also tried using a modified version of this >> > >> > >> > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> >> > >> > >> > EnvironmentVariables >> > >> > PATH >> > /sbin:/usr/sbin:/bin:/usr/bin >> > RUBYLIB >> > /usr/lib/ruby/site_ruby/1.8/ >> > >> > Label >> > com.puppetlabs.puppet >> > KeepAlive >> > >> > ProgramArguments >> > >> > /usr/bin/puppet >> > agent >> > --verbose >> > --no-daemonize >> > --logdest >> > console >> > >> > RunAtLoad >> > >> > ServiceDescription >> > Puppet Daemon >> > ServiceIPC >> > >> > StandardErrorPath >> > /var/log/puppet/puppet.err >> > StandardOutPath >> > /var/log/puppet/puppet.out >> > >> > >> > >> > >> > -- >> > 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/0b798c59-e87c-4dde-886f-885b1a2045ea%40googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> Hi Ryan, >> >> Unfortunately the plist at that link is a little out of date. The >> ServiceIPC and ServiceDescription keys aren't supported in recent >> versions of OSX. You can just remove them, really. Also, how did you >> install puppet, which version of puppet did you install, and on what >> version of OSX? Puppet >= 3.4.0 installed via dmg lives in >> /Library/Ruby/Site, to make it compatible with ruby 2 on Mavericks, so >> you may want to update the plist to reflect this. Puppet < 3.4.0 >> installed via dmg is installed to the "RUBYLIB" in your plist. >> Finally, if you're using mavericks and installing from dmg, you'll >> need facter 1.7.5-rc1 or later (I believe we are shipping the final >> version of facter 1.7.5 very soon). >> >> -- >> Moses Mendoza >> Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco - >> http://bit.ly/pupconf14 > >
Re: [Puppet Users] puppet post install launchd osx
On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb wrote: > I'm having a an issue with running puppet as launchd. I'm using this > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plist and on > some macs it will run and start at reboot and on others it doesnt. > > According to the logs puppet is exiting with a code of 1. What can i due to > ensure that the puppet launchd mod runs uninhibited. > > http://pastebin.com/raw.php?i=CX56cucf > > I've also tried using a modified version of this > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > > > EnvironmentVariables > > PATH > /sbin:/usr/sbin:/bin:/usr/bin > RUBYLIB > /usr/lib/ruby/site_ruby/1.8/ > > Label > com.puppetlabs.puppet > KeepAlive > > ProgramArguments > > /usr/bin/puppet > agent > --verbose > --no-daemonize > --logdest > console > > RunAtLoad > > ServiceDescription > Puppet Daemon > ServiceIPC > > StandardErrorPath > /var/log/puppet/puppet.err > StandardOutPath > /var/log/puppet/puppet.out > > > > > -- > 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/0b798c59-e87c-4dde-886f-885b1a2045ea%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. Hi Ryan, Unfortunately the plist at that link is a little out of date. The ServiceIPC and ServiceDescription keys aren't supported in recent versions of OSX. You can just remove them, really. Also, how did you install puppet, which version of puppet did you install, and on what version of OSX? Puppet >= 3.4.0 installed via dmg lives in /Library/Ruby/Site, to make it compatible with ruby 2 on Mavericks, so you may want to update the plist to reflect this. Puppet < 3.4.0 installed via dmg is installed to the "RUBYLIB" in your plist. Finally, if you're using mavericks and installing from dmg, you'll need facter 1.7.5-rc1 or later (I believe we are shipping the final version of facter 1.7.5 very soon). -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14 -- 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%2B421WYsV%2BEdpofVtmhTOWoauBBcfH8bUbCFr%2BrDn-AT3Xb9Hw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Unable to start puppetmaster on Mac OSX Mavericks
Hi Ryan, Can you start the puppetmaster manually, e.g. from terminal, with `puppet master --no-daemonize --verbose --debug`? What's the output? On Sun, Feb 9, 2014 at 5:18 PM, Ryan Nideffer wrote: > I've followed the installation guide for Mac OSX and I get this in > puppetmaster.err upon starting the daemon with launchctl: > > Error: Could not create resources for managing Puppet's files and > directories in sections [:main, :master, :ssl, :metrics]: undefined method > `each' for nil:NilClass > > Error: Could not prepare for execution: Could not create resources for > managing Puppet's files and directories in sections [:main, :master, :ssl, > :metrics]: undefined method `each' for nil:NilClass > > undefined method `each' for nil:NilClass > > ($:/var/log/puppet)- ruby -v > > ruby 2.0.0p247 (2013-06-27 revision 41674) [universal.x86_64-darwin13] > > Puppet v3.4.2 > > ($:/var/log/puppet)- ls -ltr /etc/puppet/ > > total 12K > > -rw-r--r-- 1 puppet puppet 4.1K Jan 6 14:39 auth.conf > > drwxrwx--x 8 puppet puppet 272 Feb 5 07:13 ssl/ > > drwxr-xr-x 2 puppet puppet 68 Feb 7 07:55 manifests/ > > -rw-r--r-- 1 puppet puppet 255 Feb 7 07:58 puppet.conf > > Any ideas? > > -- > 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/580faa3b-fdb5-4f65-b263-3104f48a78da%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14 -- 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%2B421WbAbnzuBAFXiKsj-nirUKoBYMpgkWY3qfZVT4K2TK%2B_xQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Post install
On Thu, Jan 23, 2014 at 10:30 AM, Jason Hatman wrote: > I have a complete and working Puppet setup. Now, I need to automate it. > Looking at the following page: > http://docs.puppetlabs.com/guides/installation.html#post-install I can see > that it wants me to set up launchd processes for OS X in order to have the > Puppet service start at boot. I just want to make sure that this is > necessary. I have a master/agent configuration. In a master/agent setup, > does it automate this by default or do I still have to setup launchd on each > machine? Yes, generally speaking you will still need some form of service management script (launchd plist) in place anywhere you want the service to by running as a service. On OSX, puppet uses launchd to manage services, so on OSX `puppet resource service 'puppet' ensure=running enable=true` will rely on the existence of a launchd plist in place on that host. > > This is a separate issue from the first one. I have completed my > puppet-dashboard setup and it's running fine. However, I've noticed that > after I reboot the machine, I no longer have any worker processes running. > I have to manually run "sudo -u puppet-dashboard env RAILS_ENV=production > script/delayed_job -p dashboard -n 4 -m start" before any they start working > again. I assumed once I converted dashboard to run in apache that this > would be automated. Am I wrong? > > 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/57ad28a4-8c88-47c3-8b2a-78bda273a456%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WZ5Uyx0dRR6gW1QHj3JfUoW007R-qmMgd4uCAUZFZkosQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet 3.4.2 with latest version of Hiera and Facter on OS X Mavericks
Hi Hesan, The code for Mavericks support in facter will be in Facter 1.7.5, which has not yet been officially released. However, this version is in release candidate (1.7.5-rc1). See the release announcement here: https://groups.google.com/forum/#!topic/puppet-users/wUwBVVJLayA. If you want to give the Release Candidate a try, download the mac package here: http://downloads.puppetlabs.com/mac/facter-1.7.5-rc1.dmg. On Thu, Jan 23, 2014 at 6:46 AM, Hesan Yousif wrote: > Sorry meant to say running with Ruby v2.0 > > > On Thursday, 23 January 2014 14:29:11 UTC, Hesan Yousif wrote: >> >> Hi guys, >> >> I know this is covered in here: >> >> https://github.com/puppetlabs/puppet/pull/1856 >> https://projects.puppetlabs.com/issues/18205 >> https://tickets.puppetlabs.com/browse/PUP-1384 >> >> But I am still having trouble getting puppet to run the simplest command; >> >> sudo puppet resource group puppet ensure=present >> >> It looks like it's because of the wrong symlink as reported in the links >> above OR something wrong with the fact that puppet is trying to run with >> ruby v2.1.0 as the error returned by running the above is: >> >> >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require': cannot load such file -- facter (LoadError) >> from >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require' >> from /Library/Ruby/Site/puppet.rb:6:in `' >> from >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require' >> from >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require' >> from /Library/Ruby/Site/puppet/util/command_line.rb:12:in `> (required)>' >> from >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require' >> from >> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in >> `require' >> from /usr/bin/puppet:3:in `' >> >> Current version of ruby is 2.0.0p247 and RVM is using system ruby. >> >> Can anyone shed light on what I need to do? Build from source? Download >> earlier versions of puppet? >> >> Help please! >> >> Thanks in advance, >> Hesan >> >> > -- > 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/9f6924b7-f825-4d4c-a97d-4dbe4930cdd3%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WbD5Cicf5pM8EjQe8kcT1iC2QErigqRhBGrwszsu6hVag%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: "You need rubygems to use Hiera"
Hi Jonathan, It appears that dhoppe/puppet actually ships an entire copy of hiera 1.0.0 and hiera-puppet inside its lib directory, which is unfortunate since hiera is now at 1.3.1 and hiera-puppet is part of puppet proper. I filed an an issue against the github repo, since this isn't an ideal approach, to say the least. On Mon, Jan 20, 2014 at 8:16 AM, Jonathan Gazeley wrote: > I fixed my own problem. Seems that when I installed dhoppe/postfix, and it > automatically included a dependency dhoppe/puppet which seems to have > overwritten some components of puppet. I immediately removed dhoppe/postfix > but didn't notice that dhoppe/puppet was still in situ. Removing this and > doing "sudo yum reinstall puppet" put back the files and it now works again. > > Cheers, > Jonathan > > > > On 20/01/14 12:19, Jonathan Gazeley wrote: > > Hi chaps, > > This morning I started running into an error. All my nodes started failing > with: > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > You need rubygems to use Hiera at > /home/ispms/PUPPETROOT/environments/common/modules/uob_ntp/manifests/init.pp:5 > on node dhcp-dev.nomadic-core.bris.ac.uk > > The master log shows: > > Jan 20 12:08:38 puppet-prod puppet-master[30673]: Puppet.features.rubygems? > is deprecated. Require rubygems in your application's entry point if you > need it. > Jan 20 12:08:38 puppet-prod puppet-master[30673]:(at > /usr/lib/ruby/site_ruby/1.8/puppet/util/feature.rb:17:in `add') > > I also read this recent thread, and none of the recommendations helped: > > http://grokbase.com/t/gg/puppet-users/1419xmhyf3/error-testing-puppet-3-x-upgrade-you-need-rubygems-to-use-hiera > > This morning a colleague of mine wrote a custom function. It looked sane to > me but I removed it in case it was broken, and it didn't help. > > I also installed a Forge module, which I later removed, and it didn't help. > > I'm running stock puppet-3.4.2 from the PL repo and we are using > hiera-1.3.0. Everything worked normally until this morning and I'm not > entirely sure where to go from here. Any suggestions of things to look at? > > Cheers, > Jonathan > > > -- > 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/52DD4BCB.30106%40bristol.ac.uk. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421Wa_8-jb8DNTBGSONEHYqbroW4pN4hvvpca9%2B4uC8%2Btx%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.4.2 OS X
Hi Jason, Pete is correct. The OSX puppet package does not ship with a launchd plist. That example appears mostly up-to-date, with the notable exception RUBYLIB (in 3.4.0 puppet moved to /Library/Ruby/Site for compatibility with Mavericks) and the ServiceDescription and ServiceIPC keys that don't exist in launchd on more recent versions of OSX. On Tue, Jan 21, 2014 at 2:42 PM, Pete Brown wrote: > I am pretty sure you still need to setup the launch daemon manually on OS X. > > On 21 January 2014 06:55, Jason Hatman wrote: >> I have my Puppet installation up and running, but I currently just run >> "puppet agent --test" to use it. As I understand it, in a master/agent >> configuration, Puppet automatically runs every 30 minutes by default as long >> as the service is running. >> With Puppet 3.4.2 on OS X, is there still a need to manually create the >> launch daemon with the instructions below? Is that included as part of the >> OS X install of Puppet 3.4.2. I'm fine with manually creating it, I just >> want to make sure that I'm not wasting time on it. >> >> http://docs.puppetlabs.com/guides/installation.html#with-launchd >> >> >> -- >> 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/81860078-0af2-4f86-9e06-d58b176f4348%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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/CAJ8DPF63sMqTWkWWXjnYVJp4OTyRsM5Y3BTgJu-1JRt5MpyMFA%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WZcPaBsDoBxBchR6H%2Bf%2Bkwm996U4LB90%3D8G6g%2BXh0d7wA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] error testing puppet 3.x upgrade: You need rubygems to use Hiera
biosversion.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/net_info.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/ipmi_product.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
>> Info: Loading facts in /var/lib/puppet/lib/facter/pacemaker.rb
>> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
>> You
>> need rubygems to use Hiera at /etc/puppet/manifests/users.pp:243 on node
>> rh6client.example.com
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>>
>>
>> On the temporary server, it has output a bunch of "Info" statements about
>> processing for auth.conf, but follows that with:
>>
>> Info: Caching node for rh6client.example.com
>> Info: Caching node for rh6client.example.com
>> Warning: Puppet.features.rubygems? is deprecated. Require rubygems in your
>> application's entry point if you need it.
>> (at /usr/lib/ruby/site_ruby/1.8/puppet/util/feature.rb:17:in `add')
>> Error: You need rubygems to use Hiera at
>> /etc/puppet/manifests/users.pp:243 on
>> node rh6client.example.com
>> Error: You need rubygems to use Hiera at
>> /etc/puppet/manifests/users.pp:243 on
>> node rh6client.example.com
>> Error: You need rubygems to use Hiera at
>> /etc/puppet/manifests/users.pp:243 on
>> node rh6client.example.com
>>
>>
>> That part of the manifest looks like this:
>>
>>
>> # used on the netflow server
>> @user { 'ncsprime':
>> home => '/var/netflow/ncsprime',
>> gid=> 'ncsprime',
>> comment=> 'Cisco NCS Prime backup file owner',
>> membership => inclusive,
>> uid=> '709844',
>> password => hiera('ncsprime_password', '!!'),
>> }
>>
>> Our /etc/puppet/hiera.yaml that I copied from our existing 2.7.14 master
>> to the promoted 3.4.2 temporary master is
>>
>> ---
>> :backends: - yaml
>>
>> :hierarchy: - secure/fqdn/%{clientcert}
>>- fqdn/%{clientcert}
>>- secure/location/%{location}
>>- location/%{location}
>>- secure/common
>>- common
>>
>> :yaml:
>>:datadir: /etc/puppet/hiera-data
>>
>>
>>
>>
>> I don't understand what I'm missing; I have the rubygems package installed
>> on both the promoted master and the client I'm trying to test with. I
>> know
>> that hiera moved into the core at 3.x and that on my real master I will
>> need
>> to uninstall the 'rubygem-hiera-puppet' package, but the client I promoted
>> to be the temporary master has never had that installed.
>>
>> Google searches for this error just turn up the "install rubygems"
>> response.
>> Brent Clark posted to this list in December with the same problem, but
>> there were no follow-up responses.
>>
>> Any suggestions as to what the problem really is, because it's *not* that
>> I'm missing rubygems.
>>
>> Thanks,
>>
>> Tim
>>
>
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure 701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> --
> 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/alpine.SOC.2.11.1401171651430.29424%40dogbert.cc.ndsu.NoDak.edu.
>
> For more options, visit https://groups.google.com/groups/opt_out.
--
Moses Mendoza
Puppet Labs
Join us at PuppetConf 2014, September 23-24 in San Francisco
--
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%2B421WYmsO4fQnUqRgFNb-BCGwm-AycKiGEEn0fcVeW1bYrmVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] trouble sharing a file in a module
On Tue, Jan 7, 2014 at 5:00 PM, Tim Dunphy wrote:
> hey all,
>
>
> Having a little trouble sharing a file as part of a module I'm attempting to
> use.
>
> This is the error that I'm seeing:
>
> [root@beta:~] #puppet agent --test --server puppet.mydomain.com
> info: Caching catalog for beta.jokefire.com
> info: Applying configuration version '1389142209'
> err:
> /Stage[main]/Cassandra/File[/etc/alternatives/cassandrahome/conf/cassandra.yaml]:
> Could not evaluate: Could not retrieve information from environment
> production source(s)
> puppet:///modules/cassandra/etc/alternatives/cassandrahome/conf/cassandra.yaml
> at /etc/puppet/modules/cassandra/manifests/init.pp:12
> notice: Finished catalog run in 1.62 seconds
>
> Here is the class definition in the module I've created to share a cassandra
> configuration file and ensure that the service is running:
>
>
> [root@puppet:/etc/puppet] #cat modules/cassandra/manifests/init.pp
> class cassandra {
>service { cassandra:
> ensure => running,
> }
>
>
>file { "/etc/alternatives/cassandrahome/conf/cassandra.yaml":
> owner => "root",
> group => "root",
> mode => 0440,
> source =>
> "puppet:///modules/cassandra/etc/alternatives/cassandrahome/conf/cassandra.yaml",
> }
> }
>
>
> Here is the file I am trying to server on the puppet server:
>
> [root@puppet:/etc/puppet] #ls -l
> modules/cassandra/file/etc/alternatives/cassandrahome/conf/cassandra.yaml
> -r--r- 1 puppet puppet 30876 Jan 7 19:42
> modules/cassandra/file/etc/alternatives/cassandrahome/conf/cassandra.yaml
Hi Tim,
I think you want the directory 'file' to be named 'files', e.g.
`/etc/puppet/modules/cassandra/files`
>
> The file is physically there and the permissions and ownership seem right to
> me.
>
> Can anyone please help me with this error?
>
> Thanks
> Tim
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>
> --
> 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/CAOZy0e%3DtKLkPu9EHaaEEF9NjSReqrgLVgoXpurEyFcq0tL6fig%40mail.gmail.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
Moses Mendoza
Puppet Labs
Join us at PuppetConf 2014, September 23-24 in San Francisco
--
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%2B421Wbc6XQusY-2QPO090x%3DNecjeK5KXA54sGTigBfhSWvYeA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
Hi all, apt.puppetlabs.com has been updated with additional architectures so the 'all' packages should install. Can you check if you still have the same issues? On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza wrote: > On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers wrote: >> I updated the repository file using the official puppet-recommended version. >> The corrected line is: >> >> deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' >> above). >> >> When I do 'apt-get update' I'm told: >> >> W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/Release Unable to >> find expected entry main/binary-armel/Packages in Meta-index file (malformed >> Release file?) >> >> >> On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: >>> >>> That's not the issue at all I think. >>> >>> Is that source.list entry from a howto? >>> >>> Have you tried the instructions here: >>> >>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu >>> >>> Because what apt is making of your configuration is plain wrong. >>> >>> On 12/10/2013 05:50 PM, Jon Yeargers wrote: >>> > If I create a '/etc/apt/sources.list.d/puppet.list' with: >>> > >>> > deb http://apt.puppetlabs.com/pool wheezy stable >>> > >>> > I get: >>> > >>> > Failed to fetch >>> > >>> > http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz >>> > 404 Not Found >>> > >>> > I'm thinking that I might need to set this up on an x86 machine and then >>> > rebuild the package file myself in a private repository. > > My apologies - this is a problem with our apt repository configuration > - we did not set it up to include architectures other than i386 and > amd64. We will be remedying this soon, so that while we may not yet > have arm-specific packages, at least our all-arch packages will 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/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Moses Mendoza > Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WbXzqYfhWW-CMjkOJb_K7gJajPZFd7St7UFVpBu17wMWg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting latest agent on debian for ARM?
On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers wrote: > I updated the repository file using the official puppet-recommended version. > The corrected line is: > > deb http://apt.puppetlabs.com squeeze main (i mistakenly entered 'wheezy' > above). > > When I do 'apt-get update' I'm told: > > W: Filed to fetch http://apt.puppetlabs.com/dists/squeeze/Release Unable to > find expected entry main/binary-armel/Packages in Meta-index file (malformed > Release file?) > > > On Tuesday, December 10, 2013 9:11:44 AM UTC-8, Felix.Frank wrote: >> >> That's not the issue at all I think. >> >> Is that source.list entry from a howto? >> >> Have you tried the instructions here: >> >> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu >> >> Because what apt is making of your configuration is plain wrong. >> >> On 12/10/2013 05:50 PM, Jon Yeargers wrote: >> > If I create a '/etc/apt/sources.list.d/puppet.list' with: >> > >> > deb http://apt.puppetlabs.com/pool wheezy stable >> > >> > I get: >> > >> > Failed to fetch >> > >> > http://apt.puppetlabs.com/pool/dists/wheezy/stable/binary-armel/Packages.gz >> > 404 Not Found >> > >> > I'm thinking that I might need to set this up on an x86 machine and then >> > rebuild the package file myself in a private repository. My apologies - this is a problem with our apt repository configuration - we did not set it up to include architectures other than i386 and amd64. We will be remedying this soon, so that while we may not yet have arm-specific packages, at least our all-arch packages will 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/0e4f7484-682f-44c9-b370-5a977d4085ee%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WbSbgMBqVzD24EQWHZ_kTLmAN2vbCMAP0ZxEwidnDwzRg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: puppetdb: how to install using the system ruby 1.9.3-p484
If you installed puppet originally using ruby 1.8.7, then all of your gems, including puppet, will be in the ruby 1.8.7 gem home, and all the binaries, including puppet, that were created by rubygems will be pointing there. Since you built ruby 1.9.3 from source, perhaps you have a separate 'gem' executable in $PREFIX/bin ($PREFIX being what you passed to `configure` ruby) since 1.9.3 ships with rubygems built-in. Long story short, reinstalling your gems using your new ruby 1.9.3 gem executable will cause the new puppet gem (and all new 1.9.3 rubygems) to use ruby 1.9.3. Note that unless you remove them, your 1.8.7 ruby, rubygems, and all 1.8.7 installed gems will still exist. On Wed, Dec 4, 2013 at 12:33 PM, machete wrote: > gem list: > > gem list > > *** LOCAL GEMS *** > > bigdecimal (1.1.0) > bundler (1.3.5) > daemon_controller (1.1.7) > facter (1.7.3) > hiera (1.3.0) > io-console (0.3) > json (1.5.5) > json_pure (1.8.1) > minitest (2.5.1) > passenger (4.0.17) > puppet (3.3.2) > rack (1.5.2) > rake (0.9.2.2) > rdoc (3.9.5) > rgen (0.6.6) > > > > > On Wednesday, December 4, 2013 3:31:26 PM UTC-5, machete wrote: >> >> Hey Moses, >> >> Thanks for the quick response. >> >> Puppet was install via ruby gem ... I know, but it is so easy. >> Ruby/rubygem are running from source. >> OS is CentOS 6.4 Linux puppetdb 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 >> 03:51:51 BST 2011 x86_64 x86_64 x86_64 GNU/Linux >> >> >> On Wednesday, December 4, 2013 3:22:56 PM UTC-5, Moses Mendoza wrote: >>> >>> How did you install puppet originally? Are you running from packages, >>> rubygem, or running from source, or some other method? >>> >>> On Wed, Dec 4, 2013 at 11:58 AM, machete wrote: >>> > Hey what gives ... ? ;) >>> > >>> > I've got a shiny new install of ruby 1.9.3-p484 ... and my 'sudo puppet >>> > resource package puppetdb ensure=latest' loads ruby 1.8.7 >>> > >>> > Would someone please point me to the instructions ( or share ) on how >>> > to get >>> > my 'sudo puppet resource package puppetdb ensure=latest' to use my ruby >>> > 1.9.3-p484? >>> > >>> > ~> ruby -v >>> > ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] >>> > ~> puppet -V >>> > 3.3.2 >>> > >>> > >>> > Cheers, >>> > >>> > 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...@googlegroups.com. >>> > To view this discussion on the web visit >>> > >>> > https://groups.google.com/d/msgid/puppet-users/4015678f-f943-4de1-8640-52caa7592f31%40googlegroups.com. >>> > >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> Moses Mendoza >>> Puppet Labs >>> >>> Join us at PuppetConf 2014, September 23-24 in San Francisco > > -- > 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/f1c72cad-09f0-4a17-8f92-7f6e09995f46%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WbBMq8C-AUkN2j_gH%3DJKAz6XRr11L1g0UGFaTCYZdmfww%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: puppetdb: how to install using the system ruby 1.9.3-p484
How did you install puppet originally? Are you running from packages, rubygem, or running from source, or some other method? On Wed, Dec 4, 2013 at 11:58 AM, machete wrote: > Hey what gives ... ? ;) > > I've got a shiny new install of ruby 1.9.3-p484 ... and my 'sudo puppet > resource package puppetdb ensure=latest' loads ruby 1.8.7 > > Would someone please point me to the instructions ( or share ) on how to get > my 'sudo puppet resource package puppetdb ensure=latest' to use my ruby > 1.9.3-p484? > > ~> ruby -v > ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] > ~> puppet -V > 3.3.2 > > > Cheers, > > 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/4015678f-f943-4de1-8640-52caa7592f31%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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%2B421WY-GknrCpQfAKzei8Emtg1y21TDNxn5FRAEQ8YY-oyERg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet 3.3.1 Available
Adrien Thebo, Andrew Parker, Iristyle, Josh Cooper, Josh Partlow, Kylo Ginsberg, Matthaus Owens, Melissa Stone, Moses Mendoza, Patrick Carlisle, Rob Braden, Spencer Krum Puppet 3.3.1 Changelog - Adrien Thebo (2): e75e9f3 (maint) rename urpmi spec to be run by default 133fd3b Revert "Merge pull request #1939 from adrienthebo/maint-rename_urpmi_spec" Andrew Parker (11): dbf515a (Maint) Convert to new block expects 33b08a3 (#22471) Rescue errors specific to the YAML parser aaa94d5 (Maint) Simplify code 82c2574 (Maint) Stop asserting nothingness c98f21d (#22471) Extract YAML interaction into shared code a2f73e2 (#22471) Remove duplication by using Puppet::Util::Yaml 8b3670f (#22384) Log 404 and 406 responses at info e603ed1 (#22530) Support both YAML and PSON 8f2967e (#22652) Parse query strings in rack w/o rack 37d1ba6 (#21971) Create test to show exploit of resource_type 9296dad (#21971) Add test for accessing based on master being at root Iristyle (1): fc505e2 (maint) Windows failing spec fixes Josh Cooper (8): 3ca7604 (Maint) TestHelper already clears global state 564ecd1 (Maint) Don't keep Tempfile open while specs are running 18f4a2e (Maint) Stop asserting nothingness 74d4d9c (Maint) Fixup whitespace 5dedacd (Maint) Remove spurious subproject commit line de65c66 (#22608) Restore the ability for master to accept pson file backups 8e7d76f (Maint) Fix typo in method name c0817e3 (#22652) Restore rack parsing of POST body parameters Josh Partlow (7): 73348b7 (#22529) Dpkg provider does not warn on package not found 3d779a7 (#22529) Rpm provider does not parse 'package foo is not installed' as a package 3751a83 (#22529) Acceptance test for puppet package resource behavior 78623a3 (maint) Convert from should to expect syntax 54f6da4 (#22529) Update acceptance test for regex fix and solaris a912111 (#22529) Handle no package message for different dpkg-query versions 26c1db1 (maint) Test of resource package does-not-exist checks stderr Kylo Ginsberg (15): 0b99949 (maint) Fix misspellings in spec tests 9ea33d2 (#22535) Add puppet version to status indirector bd618e6 (#22535) Revert to yaml when a new agent talks to old master 8679795 (#22535) Fix apply/etc by setting the status_terminus per application c290dc5 (#22535) Cleanup of desc/hook for new settings 58cb39c (#22535) Improve notice message for backward compatibility 53e22cc (#22535) Add tests for backward compatibility settings 3be9d11 (#22535) Add test for legacy yaml serialization of arrays in query string c48a9b3 (#22535) Fix an exception msg; cosmetic. f97829b (#22535) Fix support for agent's status endpoint 76889b4 (#22535) Make a full status object the default in agent spec tests. 70a18ef (#22535) Use a response header for version 8ff491f (#22652) Add be_one_of matcher (copped from pcarlisle) 391c5c4 (#22652) Tighten up spec for multi-valued params in a POST body d26a0f0 (maint) Move constant outside shared_examples_for to avoid "already initialized" warning Matthaus Owens (1): bbdafe5 (#22474) Update forge/repository.rb to conditionally include zlib Melissa Stone (1): 976e051 (packaging) Update PUPPETVERSION for 3.3.1-rc3 Moses Mendoza (2): f4ce874 (packaging) Update PUPPETVERSION for 3.3.1-rc1 ae6e887 (packaging) Update PUPPETVERSION for 3.3.1 Patrick Carlisle (7): d3f263b (maint) Don't use subject in parsedfile spec e1dcea4 (#19994) Ensure that failed ParsedFile operations are marked flushed f308d1e (#21975) Don't monkey patch Object#instance_variables 65ce0ea (#22471) Finish removing duplication of yaml exceptions 7f4f0b9 (#22772) Fix test for saving empty data 5a4feef (#22772) Allow a PUT with an empty body 513d8b5 (#22772) Add error checking to yaml format Rob Braden (1): 891fce7 (packaging) Update PUPPETVERSION for 3.3.1-rc2 Spencer Krum (1): f47a4b7 Doc cleanup on create_resources example -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet 3.3.1-rc1 Available
- Andrew Parker, Josh Cooper, Josh Partlow, Kylo Ginsberg, Matthaus Owens, Moses Mendoza, Patrick Carlisle Puppet 3.3.1-rc1 Changelog Andrew Parker (8): dbf515a (Maint) Convert to new block expects 33b08a3 (#22471) Rescue errors specific to the YAML parser aaa94d5 (Maint) Simplify code 82c2574 (Maint) Stop asserting nothingness c98f21d (#22471) Extract YAML interaction into shared code a2f73e2 (#22471) Remove duplication by using Puppet::Util::Yaml 8b3670f (#22384) Log 404 and 406 responses at info e603ed1 (#22530) Support both YAML and PSON Josh Cooper (7): 3ca7604 (Maint) TestHelper already clears global state 564ecd1 (Maint) Don't keep Tempfile open while specs are running 18f4a2e (Maint) Stop asserting nothingness 74d4d9c (Maint) Fixup whitespace 5dedacd (Maint) Remove spurious subproject commit line de65c66 (#22608) Restore the ability for master to accept pson file backups 8e7d76f (Maint) Fix typo in method name Josh Partlow (5): 73348b7 (#22529) Dpkg provider does not warn on package not found 3d779a7 (#22529) Rpm provider does not parse 'package foo is not installed' as a package 3751a83 (#22529) Acceptance test for puppet package resource behavior 78623a3 (maint) Convert from should to expect syntax 54f6da4 (#22529) Update acceptance test for regex fix and solaris Kylo Ginsberg (12): 0b99949 (maint) Fix misspellings in spec tests 9ea33d2 (#22535) Add puppet version to status indirector bd618e6 (#22535) Revert to yaml when a new agent talks to old master 8679795 (#22535) Fix apply/etc by setting the status_terminus per application c290dc5 (#22535) Cleanup of desc/hook for new settings 58cb39c (#22535) Improve notice message for backward compatibility 53e22cc (#22535) Add tests for backward compatibility settings 3be9d11 (#22535) Add test for legacy yaml serialization of arrays in query string c48a9b3 (#22535) Fix an exception msg; cosmetic. f97829b (#22535) Fix support for agent's status endpoint 76889b4 (#22535) Make a full status object the default in agent spec tests. 70a18ef (#22535) Use a response header for version Matthaus Owens (1): bbdafe5 (#22474) Update forge/repository.rb to conditionally include zlib Moses Mendoza (1): f4ce874 (packaging) Update PUPPETVERSION for 3.3.1-rc1 Patrick Carlisle (4): d3f263b (maint) Don't use subject in parsedfile spec e1dcea4 (#19994) Ensure that failed ParsedFile operations are marked flushed f308d1e (#21975) Don't monkey patch Object#instance_variables 65ce0ea (#22471) Finish removing duplication of yaml exceptions -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] creating a (mac) package from a known good source + local patches
Hi Clay, Thanks for the patch! We'll take a look. Switching over to pkgbuild has been on the list for awhile. Cheers, Moses On Thu, Jul 25, 2013 at 3:45 PM, Clay Caviness wrote: > Thanks, Moses. I'll update our internal build process to use this method. > > Also, FYI, I created https://github.com/puppetlabs/packaging/pull/171 to > update the apple task to use pkgbuild instead of PackageMaker (since that > was easier than trying to find and install packagemaker...) > > > On Wed, Jul 24, 2013 at 7:38 PM, Moses Mendoza wrote: >> >> Hi Clay, >> >> I totally see your use case. We're currently looking to revisit the >> way we build apple packages to make things more sane. >> >> In the meantime, there is a workaround workflow, which still uses >> git/github but allows you to keep things offline after you download >> them. As noted in the ticket, the packaging tasks rely on our >> projects' git code info, so we have to keep that around to build. If >> you don't want to rsync around git clones, one way I've accomplished >> it is using git bundles[1] (like a git archive, but retains the >> version control info). This process is the same for facter, puppet, >> and hiera. >> >> Roughly: >> >> Clone facter and check out the tag that you want to build, e.g. 1.7.2. >> The tags we push to github are the canonical artifacts we use to mark >> a release. >># git clone git://github.com/puppetlabs/facter && cd facter && git >> checkout 1.7.2 >> >> We sign our tags, so you can verify the tag if you have our public key >> installed (see [2] on how to get it) >># git verify-tag 1.7.2 >> >> Create a git bundle of your clone >># git bundle create facter_bundle HEAD --tags >> >> Clone the packaging repo and create a git archive of it as well. 0.2.0 >> is the most recent version >># git clone git://github.com/puppetlabs/packaging && cd packaging >> && git checkout 0.2.0 >># git bundle create packaging_bundle HEAD --tags >> >> With the two git bundle files, you can now create mac packages >> offline. Take the git bundles to wherever you want to build packages, >> and git clone then to extract. >> # git clone facter_bundle facter >> # git clone packaging_bundle facter/ext/packaging >> # apply your patches to facter (even branch and commit them if you want) >> >> Now build packages: >> # cd facter && rake package:apple ; # a dmg will be staged in >> ./pkg/apple/ >> >> I completely understand your concern about the tasks talking to github >> - some of them do. However, rake package:apple isn't one of them - it >> relies entirely on tools present on the system. >> >> [1] http://git-scm.com/blog/2010/03/10/bundles.html >> [2] http://puppetlabs.com/misc/download-options >> >> On Wed, Jul 24, 2013 at 2:28 PM, Clay Caviness >> wrote: >> > I need to have a way to re-create the installation package we use for >> > facter >> > and puppet, offline, from a known-good source. Often, we have local >> > patches >> > (e.g., backporting certain providers from 3.x to 2.x because our servers >> > are >> > still on 2.x, or patching things not yet released upstream), so our >> > process >> > has been: >> > >> > 1) Download tarball for a given release >> > 2) Update makefile we use to create package to refer to new tarball >> > 3) Verify local patches are still required >> > 4) Build (possibly patched) package using ./etc/osx/createpackage.sh >> > >> > Now that createpackage.sh is really fully deprecated and gone, I'm >> > looking >> > at the rake packaging tasks. As I found in >> > http://projects.puppetlabs.com/issues/21760#note-4 the tarball is >> > useless >> > since the rake tasks assume you're in a git checkout. >> > >> > So now I'm at a bit of a loss on how to create these packages. Checkout >> > a >> > specific tag, and then make my own tarball? I'm concerned that the >> > reliance >> > on it being a git checkout means the tasks may end up talking to github, >> > making the whole process not hermetic. >> > >> > What's the best solution for this? Shall I create this as an issue >> > against >> > the packaging tasks? >> > >> > Thanks >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Gro
Re: [Puppet Users] creating a (mac) package from a known good source + local patches
Hi Clay, I totally see your use case. We're currently looking to revisit the way we build apple packages to make things more sane. In the meantime, there is a workaround workflow, which still uses git/github but allows you to keep things offline after you download them. As noted in the ticket, the packaging tasks rely on our projects' git code info, so we have to keep that around to build. If you don't want to rsync around git clones, one way I've accomplished it is using git bundles[1] (like a git archive, but retains the version control info). This process is the same for facter, puppet, and hiera. Roughly: Clone facter and check out the tag that you want to build, e.g. 1.7.2. The tags we push to github are the canonical artifacts we use to mark a release. # git clone git://github.com/puppetlabs/facter && cd facter && git checkout 1.7.2 We sign our tags, so you can verify the tag if you have our public key installed (see [2] on how to get it) # git verify-tag 1.7.2 Create a git bundle of your clone # git bundle create facter_bundle HEAD --tags Clone the packaging repo and create a git archive of it as well. 0.2.0 is the most recent version # git clone git://github.com/puppetlabs/packaging && cd packaging && git checkout 0.2.0 # git bundle create packaging_bundle HEAD --tags With the two git bundle files, you can now create mac packages offline. Take the git bundles to wherever you want to build packages, and git clone then to extract. # git clone facter_bundle facter # git clone packaging_bundle facter/ext/packaging # apply your patches to facter (even branch and commit them if you want) Now build packages: # cd facter && rake package:apple ; # a dmg will be staged in ./pkg/apple/ I completely understand your concern about the tasks talking to github - some of them do. However, rake package:apple isn't one of them - it relies entirely on tools present on the system. [1] http://git-scm.com/blog/2010/03/10/bundles.html [2] http://puppetlabs.com/misc/download-options On Wed, Jul 24, 2013 at 2:28 PM, Clay Caviness wrote: > I need to have a way to re-create the installation package we use for facter > and puppet, offline, from a known-good source. Often, we have local patches > (e.g., backporting certain providers from 3.x to 2.x because our servers are > still on 2.x, or patching things not yet released upstream), so our process > has been: > > 1) Download tarball for a given release > 2) Update makefile we use to create package to refer to new tarball > 3) Verify local patches are still required > 4) Build (possibly patched) package using ./etc/osx/createpackage.sh > > Now that createpackage.sh is really fully deprecated and gone, I'm looking > at the rake packaging tasks. As I found in > http://projects.puppetlabs.com/issues/21760#note-4 the tarball is useless > since the rake tasks assume you're in a git checkout. > > So now I'm at a bit of a loss on how to create these packages. Checkout a > specific tag, and then make my own tarball? I'm concerned that the reliance > on it being a git checkout means the tasks may end up talking to github, > making the whole process not hermetic. > > What's the best solution for this? Shall I create this as an issue against > the packaging tasks? > > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Moses Mendoza Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Final Countdown discount - save 15%! -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announce: Puppet 3.2.3 Available
Hi Justin, Yes, I'll try to get those up today. Moses On Wed, Jul 17, 2013 at 3:37 PM, Justin Brown wrote: > Moses, > > The Fedora 19 packages have not been updated. Could you issue packages for > http://yum.puppetlabs.com/fedora/f19/? > > Thanks, > Justin > > > On Mon, Jul 15, 2013 at 2:18 PM, Moses Mendoza wrote: >> >> 3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some >> Windows bugs introduced in 3.2.0, as well as a few performance >> problems and miscellaneous bugs. >> >> === >> ## Puppet 3.2.3 Downloads ## >> === >> >> Source: https://downloads.puppetlabs.com/puppet/puppet-3.2.3.tar.gz >> >> RPM and deb packages available in the Puppet Labs repositories at: >> http://yum.puppetlabs.com and http://apt.puppetlabs.com >> >> Gems are available via rubygems at >> https://rubygems.org/downloads/puppet-3.2.3.gem >> or by using `gem install puppet` >> >> Mac package is available at >> https://downloads.puppetlabs.com/mac/puppet-3.2.3.dmg >> >> Windows package is available at >> https://downloads.puppetlabs.com/windows/puppet-3.2.3.msi >> >> Please report feedback via the Puppet Labs Redmine site, using an >> affected puppet version of 3.2.3: >> https://projects.puppetlabs.com/projects/puppet/ >> >> ======== >> ## Puppet 3.2.3 Contributors ## >> >> >> Adrien Thebo, Andrew Parker, Dustin J. Mitchell, Josh Cooper, Josh >> Partlow, Justin Stoller, Matthaus Owens, Moses Mendoza, Nick >> Fagerlund, Patrick Carlisle >> >> = >> ## Puppet 3.2.3 Release Notes ## >> = >> >> ### Windows Fixes >> >> This release fixes several Windows bugs that couldn't be targeted for >> earlier 3.2 releases. >> >> * [#20768: windows user provider can not manage password or home >> directory](https://projects.puppetlabs.com/issues/20768) --- This was >> a regression in 3.2.0/3.2.1. >> * [#21043: setting in puppet.conf ignored on Windows in Puppet >> 3.2.1](https://projects.puppetlabs.com/issues/21043) --- This was a >> regression in 3.2.0/3.2.1. >> * [#16080: Service provider broken in Windows Server >> 2012](https://projects.puppetlabs.com/issues/16080) --- This affected >> all previous Puppet versions. >> * [#20787: 'puppet resource group' takes incredibly long on >> Windows](https://projects.puppetlabs.com/issues/20787) --- This >> affected all previous Puppet versions. >> * [#20302: Windows File.executable? now returns false on ruby >> 1.9](https://projects.puppetlabs.com/issues/20302) >> * [#21280: Don't create c:\dev\null in windows >> specs](https://projects.puppetlabs.com/issues/21280) --- This was only >> relevant to Puppet developers. >> >> ### Logging and Reporting Fixes >> >> * [#20383: Bring back helpful error messages like prior to Puppet >> 3](https://projects.puppetlabs.com/issues/20383) --- This was a >> regression from 3.0.0, which caused file names and line numbers to >> disappear from duplicate resource declaration errors. >> * [#20900: tagmail triggers in --onetime mode without changes after >> upgrade from 3.1.1 to >> 3.2.1](https://projects.puppetlabs.com/issues/20900) --- This was a >> regression in 3.2.0/3.2.1. >> * [#20919: Logging behaviour issues in >> 3.2.1](https://projects.puppetlabs.com/issues/20919) --- This was a >> regression in 3.2.0/3.2.1, which caused noisy logging to the console >> even if the `--logdest` option was set. >> >> ### Performance Fixes >> >> * [#21376: Stack level too deep after updating from 3.1.1 to >> 3.2.2](https://projects.puppetlabs.com/issues/21376) --- This would >> sometimes cause total failures when importing a large number of >> manifest files (such as with the `import nodes/*.pp` idiom). >> * [#21320: Puppet daemon may sleep for 100 years after receiving USR1 >> on 64 bit systems](https://projects.puppetlabs.com/issues/21320) --- >> MCollective's Puppet plugin uses puppet agent's USR1 signal to trigger >> a run if the agent is running; on 64-bit systems, this could cause >> puppet agent to keep running, but stop doing scheduled configuration >> runs. This was caused by a bug in Ruby \< 2.0, but we modified Puppet >> to work around it. >> * [#20901: `puppet --version` is unnecessarily >> slow](https://projects.puppetlabs.com/issues/20901) --- This was a >> regression in 3.2.0/3.2.1. >> >> ###
[Puppet Users] Announce: Puppet 3.2.3 Available
3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some
Windows bugs introduced in 3.2.0, as well as a few performance
problems and miscellaneous bugs.
===
## Puppet 3.2.3 Downloads ##
===
Source: https://downloads.puppetlabs.com/puppet/puppet-3.2.3.tar.gz
RPM and deb packages available in the Puppet Labs repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Gems are available via rubygems at
https://rubygems.org/downloads/puppet-3.2.3.gem
or by using `gem install puppet`
Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-3.2.3.dmg
Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-3.2.3.msi
Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.2.3:
https://projects.puppetlabs.com/projects/puppet/
## Puppet 3.2.3 Contributors ##
Adrien Thebo, Andrew Parker, Dustin J. Mitchell, Josh Cooper, Josh
Partlow, Justin Stoller, Matthaus Owens, Moses Mendoza, Nick
Fagerlund, Patrick Carlisle
=
## Puppet 3.2.3 Release Notes ##
=
### Windows Fixes
This release fixes several Windows bugs that couldn't be targeted for
earlier 3.2 releases.
* [#20768: windows user provider can not manage password or home
directory](https://projects.puppetlabs.com/issues/20768) --- This was
a regression in 3.2.0/3.2.1.
* [#21043: setting in puppet.conf ignored on Windows in Puppet
3.2.1](https://projects.puppetlabs.com/issues/21043) --- This was a
regression in 3.2.0/3.2.1.
* [#16080: Service provider broken in Windows Server
2012](https://projects.puppetlabs.com/issues/16080) --- This affected
all previous Puppet versions.
* [#20787: 'puppet resource group' takes incredibly long on
Windows](https://projects.puppetlabs.com/issues/20787) --- This
affected all previous Puppet versions.
* [#20302: Windows File.executable? now returns false on ruby
1.9](https://projects.puppetlabs.com/issues/20302)
* [#21280: Don't create c:\dev\null in windows
specs](https://projects.puppetlabs.com/issues/21280) --- This was only
relevant to Puppet developers.
### Logging and Reporting Fixes
* [#20383: Bring back helpful error messages like prior to Puppet
3](https://projects.puppetlabs.com/issues/20383) --- This was a
regression from 3.0.0, which caused file names and line numbers to
disappear from duplicate resource declaration errors.
* [#20900: tagmail triggers in --onetime mode without changes after
upgrade from 3.1.1 to
3.2.1](https://projects.puppetlabs.com/issues/20900) --- This was a
regression in 3.2.0/3.2.1.
* [#20919: Logging behaviour issues in
3.2.1](https://projects.puppetlabs.com/issues/20919) --- This was a
regression in 3.2.0/3.2.1, which caused noisy logging to the console
even if the `--logdest` option was set.
### Performance Fixes
* [#21376: Stack level too deep after updating from 3.1.1 to
3.2.2](https://projects.puppetlabs.com/issues/21376) --- This would
sometimes cause total failures when importing a large number of
manifest files (such as with the `import nodes/*.pp` idiom).
* [#21320: Puppet daemon may sleep for 100 years after receiving USR1
on 64 bit systems](https://projects.puppetlabs.com/issues/21320) ---
MCollective's Puppet plugin uses puppet agent's USR1 signal to trigger
a run if the agent is running; on 64-bit systems, this could cause
puppet agent to keep running, but stop doing scheduled configuration
runs. This was caused by a bug in Ruby \< 2.0, but we modified Puppet
to work around it.
* [#20901: `puppet --version` is unnecessarily
slow](https://projects.puppetlabs.com/issues/20901) --- This was a
regression in 3.2.0/3.2.1.
### Misc Fixes
* [#21264: parser = future breaks executing functions as class
defaults](https://projects.puppetlabs.com/issues/21264)
### All 3.2.3 Changes
[See here for a list of all changes in the 3.2.3
release.](https://projects.puppetlabs.com/versions/410)
==
## Puppet 3.2.3 Changelog ##
==
Adrien Thebo (1):
6a0127f (#20383) Provide location of duplicate resource in error
Andrew Parker (2):
f19c8f2 (Maint) Cleanup specs
ec6b51a (#21264) Update rgen dependency to 0.6.5
Dustin J. Mitchell (1):
b1a5092 clean up docs for new parser functions
Josh Cooper (16):
b4f84e1 (#20787) Do not generate NetBIOS name service requests
ba3c4c2 Revert "Merge pull request #1478 from
dsd/fix/master/18781-webrick-old-client-compat"
694f97d (#20302) Windows ruby 1.8 workarounds are not necessary in 1.9
ca8602e (#20302) Append .exe to spec "executables" on Windows
6503925 (#20302) Handle nested include filters
54bb9e4 (#20302) File.expand_file('~') fails differently in Ruby19
848eb63 Maint: Don't execute facter during spec tests
28fb267 Maint: Fix typo
[Puppet Users] Announce: Puppet 3.2.3-rc1 Available
**Release candidate:** This version entered RC on July 2, 2013. It has not yet been officially released. 3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some Windows bugs introduced in 3.2.0, as well as a few performance problems and miscellaneous bugs. = ## Puppet 3.2.3-rc1 Downloads ## = Source: https://downloads.puppetlabs.com/puppet/puppet-3.2.3-rc1.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.3.rc1.gem or by using `gem install --pre puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.3-rc1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.3-rc1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.3-rc1: https://projects.puppetlabs.com/projects/puppet/ == ## Puppet 3.2.3-rc1 Contributors ## == Adrien Thebo, Andrew Parker, Dustin J. Mitchell, Josh Cooper, Josh Partlow, Justin Stoller, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Patrick Carlisle ## Puppet 3.2.3-rc1 Release Notes ## ### Windows Fixes This release fixes several Windows bugs that couldn't be targeted for earlier 3.2 releases. * [#20768: windows user provider can not manage password or home directory](https://projects.puppetlabs.com/issues/20768) --- This was a regression in 3.2.0/3.2.1. * [#21043: setting in puppet.conf ignored on Windows in Puppet 3.2.1](https://projects.puppetlabs.com/issues/21043) --- This was a regression in 3.2.0/3.2.1. * [#16080: Service provider broken in Windows Server 2012](https://projects.puppetlabs.com/issues/16080) --- This affected all previous Puppet versions. * [#20787: 'puppet resource group' takes incredibly long on Windows](https://projects.puppetlabs.com/issues/20787) --- This affected all previous Puppet versions. * [#20302: Windows File.executable? now returns false on ruby 1.9](https://projects.puppetlabs.com/issues/20302) * [#21280: Don't create c:\dev\null in windows specs](https://projects.puppetlabs.com/issues/21280) --- This was only relevant to Puppet developers. ### Logging and Reporting Fixes * [#20383: Bring back helpful error messages like prior to Puppet 3](https://projects.puppetlabs.com/issues/20383) --- This was a regression from 3.0.0, which caused file names and line numbers to disappear from duplicate resource declaration errors. * [#20900: tagmail triggers in --onetime mode without changes after upgrade from 3.1.1 to 3.2.1](https://projects.puppetlabs.com/issues/20900) --- This was a regression in 3.2.0/3.2.1. * [#20919: Logging behaviour issues in 3.2.1](https://projects.puppetlabs.com/issues/20919) --- This was a regression in 3.2.0/3.2.1, which caused noisy logging to the console even if the `--logdest` option was set. ### Performance Fixes * [#21376: Stack level too deep after updating from 3.1.1 to 3.2.2](https://projects.puppetlabs.com/issues/21376) --- This would sometimes cause total failures when importing a large number of manifest files (such as with the `import nodes/*.pp` idiom). * [#21320: Puppet daemon may sleep for 100 years after receiving USR1 on 64 bit systems](https://projects.puppetlabs.com/issues/21320) --- MCollective's Puppet plugin uses puppet agent's USR1 signal to trigger a run if the agent is running; on 64-bit systems, this could cause puppet agent to keep running, but stop doing scheduled configuration runs. This was caused by a bug in Ruby \< 2.0, but we modified Puppet to work around it. * [#20901: `puppet --version` is unnecessarily slow](https://projects.puppetlabs.com/issues/20901) --- This was a regression in 3.2.0/3.2.1. ### Misc Fixes * [#21264: parser = future breaks executing functions as class defaults](https://projects.puppetlabs.com/issues/21264) ### All 3.2.3 Changes [See here for a list of all changes in the 3.2.3 release.](https://projects.puppetlabs.com/versions/410) = ## Puppet 3.2.3-rc1 Changelog ## = Adrien Thebo (1): 6a0127f (#20383) Provide location of duplicate resource in error Andrew Parker (2): f19c8f2 (Maint) Cleanup specs ec6b51a (#21264) Update rgen dependency to 0.6.5 Dustin J. Mitchell (1): b1a5092 clean up docs for new parser functions Josh Cooper (16): b4f84e1 (#20787) Do not generate NetBIOS name service requests ba3c4c2 Revert "Merge pull request #1478 from dsd/fix/master/18781-webrick-old-client-compat" 694f97d (#20302) Windows ru
[Puppet Users] Ubuntu 11.10 leaving apt.puppetlabs.com
Ubuntu 11.10 Oneiric Ocelot reached end of life on 2013-05-09 [1], so we are no longer building new packages for it and it will be removed from our apt repository on Friday, July 9. [1] https://lists.ubuntu.com/archives/ubuntu-announce/2013-May/000174.html -- Moses Mendoza Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Enterprise 3.0 now available!
On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien wrote: > Hello > > It is difficult to find what's inside Puppet Enterprise (which puppet > version, etc...). > I'm particularly interested to understand what was changed to have such gain > in performances. > > Thanks > > Aurélien > Hi Aurélien, Please see http://docs.puppetlabs.com/pe/latest/overview_whats_new.html to for new component versions, improvements, etc. in PE 3.0. Moses > > Le 25/06/2013 15:37, Nigel Kersten a écrit : > >> Hello puppet-users, >> >> Puppet Enterprise 3.0 is now available now. You can download it now here: >> http://puppetlabs.com/misc/pe-files/ >> >> >> This major release introduces the following new capabilities: >> >> * Enhanced performance and scalability: 200% performance boost and 100% >> increase in scalability helps you move faster and respond more quickly to >> changing business needs >> * New orchestration capabilities: Dynamically discover resources, then >> fully orchestrate complex management operations on large volumes of cloud >> nodes using Puppet Enterprise's orchestration engine. >> * Software-defined infrastructure: Automate the management of not just >> compute resources, but also network and storage resources, with Puppet >> Enterprise's unified, software-defined approach >> >> You can get a full overview of all of the new Puppet Enterprise >> capabilities here: >> https://puppetlabs.com/puppet/whats-new/ >> >> Or review the docs here: >> https://docs.puppetlabs.com/pe/3.0/ >> >> I'm hosting live technical webinars and demo on Thursday, June 27. >> Register today: https://puppetlabs.com/resources/webinars/ >> >> We hope you enjoy this release, and looking forward to your feedback! >> >> >> Nigel Kersten >> CTO, Puppet Labs >> @nigelkersten >> >> >> -- >> 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 post to this group, send email to puppet-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Moses Mendoza Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Fair point. The documentation was written before we built & shipped
our ruby 1.8.7 for el5, and was not updated to reflect the fact that
this is now available via the Puppet Labs yum repositories. I'll make
sure this gets updated.
On Thu, Mar 21, 2013 at 12:48 PM, Dan White wrote:
> The documentation is a bit contradictory.
>
> It says you need ruby 1.8.7, and then says you cannot use it with
> CentOS/RHEL-5 'cause the supported version of ruby is <1.8.7
> It totally ignores the Puppet dependencies repos, which contain ruby 1.8.7
>
> “Sometimes I think the surest sign that intelligent life exists elsewhere in
> the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
>
> ____
> From: "Moses Mendoza"
> To: puppet-users@googlegroups.com, puppet-...@googlegroups.com,
> puppet-annou...@googlegroups.com
> Sent: Thursday, March 21, 2013 3:28:46 PM
> Subject: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
>
>
> Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of
> Puppet Dashboard with bug fixes and minor features.
>
> This release is available for download at:
> https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz
>
> Available in native package format in the Puppet Labs yum and apt
> repositories at:
> http://yum.puppetlabs.com and http://apt.puppetlabs.com
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected version of 1.2.23:
> http://projects.puppetlabs.com/projects/dashboard
>
> Documentation is available at:
> http://docs.puppetlabs.com/dashboard/index.html
>
> Contributors:
> Aaron Stone, Daniel Pittman, Dustin J. Mitchell, Ken Barber, Matthaus
> Owens, Moses Mendoza, and fhrbek
>
> =
> ## Puppet Dashboard 1.2.23 Release Notes ##
> =
> Comment out specific gem rack version in our vendored Rails
>
> * addresses http://projects.puppetlabs.com/issues/11669
>
> (#17914) Store FlashHash as a normal Hash in session
>
> This patch is a backport of:
>
>
> https://github.com/rails/rails/commit/36376560fdd02f955ae3bf6b7792b784443660ad
>
> In the form of a monkey patch in the puppet-dashboard initializer stage.
>
> This is required to allow puppet-dashboard to co-exist with other
> applications
> that do not have the full rails stack in their namespace. Without it,
> other
> non-rails applications (such as the certificate service and live
> management)
> are unable to unmarshal cookies created in Rails. Instead, they
> invalidate the
> session and we start to see weird authentication glitches in the GUI.
>
> In essence this patch ensures that when the FlashHash data is
> stored in a cookie
> it is stored as a normal Ruby Hash, as apposed to an
> ActionController::Flash::FlashHash. As all other Ruby applications
> should be
> able to unmarshal a Hash, this will avoid the Marshal.load method in
> Rack::Session::Cookie from throwing a NameError exception.
>
> Signed-off-by: Ken Barber
>
> Add addgroup, addclass, listgroups, listclasses tasks for nodes
>
> Previously if a user wanted to use rake tasks to interrogate the
> dashboard
> about which groups or classes a node belonged to, they would be out of
> luck.
> Similarly, if a user wanted to add a class or group to a node
> without replacing
> the already assigned classes/groups of a node it was not possible via
> only
> rake. This commit adds a task in the node namespace to add a group
> or groups to
> a node and to add a class or classes to a node. The other two
> tasks added here
> list out the groups or classes already assigned to a node.
>
> (#16429) Fix relative URLs of icons in tables.css
>
> These links work when puppet-dashboard is at the top level because
> browsers treat /../ as equivalent to /.
>
> ==
> ## Puppet Dashboard 1.2.23 Changelog ##
> ==
> Aaron Stone (11):
> e56a1dd Travis for master branch.
> 5584128 Issue 11760: Remove unused Services view.
> 2c9c954 Bug fix: inherited_resources using deprecated
> {{mustache}} syntax instead of %{newer} syntax
> a4b73a9 Spec fix to 04b4c0f use should be_any instead of array
> indexing.
> b98ef7e Node and Group parameters rake tasks should not create
> duplicate entries. Fixes #13867, updates commit 0108c040 to behave as
> intended.
> 792d74a Check that the reports import dir exists, is a
> directory, is readable. #18512
> 7bc9438 puts is S
[Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of
Puppet Dashboard with bug fixes and minor features.
This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz
Available in native package format in the Puppet Labs yum and apt
repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.23:
http://projects.puppetlabs.com/projects/dashboard
Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html
Contributors:
Aaron Stone, Daniel Pittman, Dustin J. Mitchell, Ken Barber, Matthaus
Owens, Moses Mendoza, and fhrbek
=
## Puppet Dashboard 1.2.23 Release Notes ##
=
Comment out specific gem rack version in our vendored Rails
* addresses http://projects.puppetlabs.com/issues/11669
(#17914) Store FlashHash as a normal Hash in session
This patch is a backport of:
https://github.com/rails/rails/commit/36376560fdd02f955ae3bf6b7792b784443660ad
In the form of a monkey patch in the puppet-dashboard initializer stage.
This is required to allow puppet-dashboard to co-exist with other
applications
that do not have the full rails stack in their namespace. Without it, other
non-rails applications (such as the certificate service and live management)
are unable to unmarshal cookies created in Rails. Instead, they
invalidate the
session and we start to see weird authentication glitches in the GUI.
In essence this patch ensures that when the FlashHash data is
stored in a cookie
it is stored as a normal Ruby Hash, as apposed to an
ActionController::Flash::FlashHash. As all other Ruby applications should be
able to unmarshal a Hash, this will avoid the Marshal.load method in
Rack::Session::Cookie from throwing a NameError exception.
Signed-off-by: Ken Barber
Add addgroup, addclass, listgroups, listclasses tasks for nodes
Previously if a user wanted to use rake tasks to interrogate the dashboard
about which groups or classes a node belonged to, they would be out of luck.
Similarly, if a user wanted to add a class or group to a node
without replacing
the already assigned classes/groups of a node it was not possible via only
rake. This commit adds a task in the node namespace to add a group
or groups to
a node and to add a class or classes to a node. The other two
tasks added here
list out the groups or classes already assigned to a node.
(#16429) Fix relative URLs of icons in tables.css
These links work when puppet-dashboard is at the top level because
browsers treat /../ as equivalent to /.
==
## Puppet Dashboard 1.2.23 Changelog ##
==
Aaron Stone (11):
e56a1dd Travis for master branch.
5584128 Issue 11760: Remove unused Services view.
2c9c954 Bug fix: inherited_resources using deprecated
{{mustache}} syntax instead of %{newer} syntax
a4b73a9 Spec fix to 04b4c0f use should be_any instead of array indexing.
b98ef7e Node and Group parameters rake tasks should not create
duplicate entries. Fixes #13867, updates commit 0108c040 to behave as
intended.
792d74a Check that the reports import dir exists, is a
directory, is readable. #18512
7bc9438 puts is STDOUT.puts
7ea8816 Change deprecated 'ftools' to 'fileutils'.
c244fa2 Daemonize in the Debian / Ubuntu server init.
2b0aad4 Tighten up code for rake api tasks, and move common
get_node get_group and get_class methods into a shared helper file.
7753bc5 Comment out specific gem rack version in our vendored Rails
Daniel Pittman (1):
e362172 (#19304) Upgrade to json_pure 1.7.7 for CVE-2013-0269
Dustin J. Mitchell (4):
775ab52 (#16429) Fix relative URLs of icons in tables.css
f37359a (#16429) fix relative links in application.scss
c7560d7 (#16429) use a controller reference for the delayed jobs link
1b1f0ee (#16429) use correct links for radiator, too
Ken Barber (1):
720da9d (#17914) Store FlashHash as a normal Hash in session
Matthaus Owens (7):
c040b17 Add addgroup, addclass, listgroups, listclasses tasks for nodes
d7d53da Fix descriptions of node tasks to match reality
f5e4a8e Add get_node helper method to node.rake
df715b4 (packaging) Update VERSION to 1.2.23-rc1
1c061e5 (maint) Make rails gems optional for rake tasks
aa33fbf (maint) Improve message during a load error in Rakefile
1dfc89b (packaging) Update VERSION to 1.2.23-rc2
Moses Mendoza (4):
65e5596 [packaging] Update mocks for rpmbuilder mock format
ea4ea37 [packaging] remove natty distribution from builds
c577d39 Update VERSION for 1.2.23-rc3
ac12e01 (packaging) Update VERSION to 1.2.23
fhrbe
Re: [Puppet Users] Hiera 1.2.0-rc2 and deep-merge
Hey Dan, Thanks for pointing this out! You're totally right. Not only does it require deep_merge, but it also appears to just fail silently if it's not there. We're looking into it now. Cheers, Moses On Mon, Mar 18, 2013 at 7:33 AM, Dan White wrote: > Stumbled around a bit until I figured out you need to do this: > >gem install deep_merge > > to get it to work ! > > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Dashboard 1.2.23-rc3 Available
Puppet Dashboard 1.2.23-rc3 is a maintenance release candidate of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23-rc3.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.23-rc3: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html Contributors: Aaron Stone = ## Puppet Dashboard 1.2.23-rc2 Release Notes ## = Comment out specific gem rack version in our vendored Rails * addresses http://projects.puppetlabs.com/issues/11669 == ## Puppet Dashboard 1.2.23-rc3 Changelog ## == Aaron Stone (1): 7753bc5 Comment out specific gem rack version in our vendored Rails Moses Mendoza (1): c577d39 Update VERSION for 1.2.23-rc3 -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Hiera 1.2.0-rc2 Available
Hiera 1.2.0-rc2 is a feature release candidate in the 1.x series with new features and bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/hiera/hiera-1.2.0-rc2.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/hiera Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/hiera-1.2.0-rc2.dmg Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.2.0-rc2: http://projects.puppetlabs.com/projects/hiera/ Fixes targeted at the final of this version in our bug tracker: http://projects.puppetlabs.com/versions/332 === ## Hiera 1.2.0-rc2 Changelog ## === Andrew Parker (13): 26311b7 (#18718) Load logger classes eagerly 2520aa3 (#18718) Create logger to handle fallback 074f5c8 (#18718) Enable console fallback when logger not suitable 8db2949 (#18718) Implement suitablity check for puppet logger dc98e2d (#17434) Add YARD for #parse_string 06dcf8e (#17434) Clarify tests for #parse_string dc6c538 (#17434) Add tests to exclude unwanted lookups 3a2660d (#17434) Stronger assertion about how keys are looked up 4d85f92 (Maint) Describe desired behavior in backend specs 023001d (#17434) Simplify string interpolation 9a3f1fd (#17434) Simplify logic around looking up values 453b489 (#17434) Support recursive interpolation 9a62bfd (#17434) Detect loops in recursive lookup Jeff McCune (2): b2623d9 (maint) Add Travis CI Support d9db368 Add contributing document to Hiera Justen Walker (3): 4ac8372 Add deep-merge feature to backend lookups 3da83b2 Allow both symbols and strings when deciding behavior of merge_answer 950076b Fix undefined method `[]' for nil:NilClass error in yaml_backend_spec.rb Matthaus Owens (1): 6414532 (packaging) Update lib/hiera.rb for 1.2.0-rc2 Patrick Carlisle (2): ea485ab (#16089) Reduce scope lookups in parse_string bd2e3d3 (#17434) Revert "Merge pull request #29 from timurbatyrshin/puppet-style" R.I.Pienaar (2): c8e3e90 16644 - should have a generic file cache aceca79 (#16644) Add a generic file cache Sharif Nassar (1): ab7fc5a Spelling. floatingatoll (1): e3c8045 comment typo fix in lib/hiera/backend.rb -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Facter 1.6.18 Available
Facter 1.6.18 is a maintenance release in the 1.6.x series with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.18.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.18.dmg Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.18: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Fixes targeted at the final of this version in our bug tracker: http://projects.puppetlabs.com/versions/362 Facter 1.6.18 includes contributions from the following people: Jakob Borg, Jeff McCune, Matthaus Owens, Moses Mendoza, Patrick Carlisle, Toby Hsieh, and scepticulous. = ## Facter 1.6.18 Changelog ## = Jakob Borg (1): bf19fb3 (#15306) Read /proc/self/status in binary mode Jeff McCune (6): 7522fde Whitespace only reflow of README b8f6abf (maint) Add Travis CI support to active branches 51de32a Fix Travis CI failures on virtualbox fbf2893 (maint) Update gem source in Gemfile aeb1aa2 (maint) Add Ruby 2.0.0 to Travis build matrix 0710181 (maint) Fix failing manufacturer spec on Solaris 10 Matthaus Owens (2): 18ba6f3 (maint) Remove rc_mocks from build_defaults 871342f (maint) Add f18 mocks to build_defaults Moses Mendoza (3): 11a4143 [packaging] Remove natty from the deb pkg list, its EOL b07bcd5 [packaging] Update mocks for rpmbuilder mock format 11e9d52 Update lib/facter/version.rb for 1.6.18-rc1 Patrick Carlisle (2): a79451a Add missing require for macaddress 7d25751 Call correct function on IP in NetMask Toby Hsieh (2): 2a6faff (#18308) Use argv in Facter::Application.parse cf3e02b Add tests for Facter::Application.parse scepticulous (1): 891a148 (#13396) Unify ifconfig usage and lookup ifconfig path to fix support for recent net-tools -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Enterprise 2.7.2 Available [ Security Release ]
Dear Puppet Enterprise Users, Puppet Enterprise 2.7.2 is now available. This is a security release of Puppet Enterprise. All users of Puppet Enterprise are strongly encouraged to upgrade when possible to Puppet Enterprise 2.7.2. Puppet Enterprise 2.7.2 includes fixes to address CVE-2013-1640, CVE-2013-1652, CVE-2013-1653, CVE-2013-1654, and CVE-2013-2275. For more information, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-1640, http://puppetlabs.com/security/cve/cve-2013-1652, http://puppetlabs.com/security/cve/cve-2013-1653, http://puppetlabs.com/security/cve/cve-2013-1654, and http://puppetlabs.com/security/cve/cve-2013-2275. As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. Thanks, Moses Mendoza Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet 3.1.1 Available [ Security Release ]
Puppet 3.1.1 is now available. 3.1.1 addresses several security vulnerabilities discovered in the 3.x line of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-1640, CVE-2013-1652, CVE-2013-1653, CVE-2013-1654, CVE-2013-1655 and CVE-2013-2275. All users of Puppet 3.1.0 and earlier are strongly encouraged to upgrade to 3.1.1. For more information on these vulnerabilities, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-1640, http://puppetlabs.com/security/cve/cve-2013-1652, http://puppetlabs.com/security/cve/cve-2013-1653, http://puppetlabs.com/security/cve/cve-2013-1654, http://puppetlabs.com/security/cve/cve-2013-1655, and http://puppetlabs.com/security/cve/cve-2013-2275. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.1.1.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-3.1.1.msi RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/puppet-3.1.1.dmg Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.1.1.gem or by using `gem install puppet --version=3.1.1` See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.1.1: http://projects.puppetlabs.com/projects/puppet/ ## Changelog ## Andrew Parker (3): 3b0178f (#14093) Cleanup tests for template functionality 4ca17d9 (#14093) Remove unsafe attributes from TemplateWrapper f1d0731 (#14093) Restore access to the filename in the template Jeff McCune (2): 52be043 (#19151) Reject SSLv2 SSL handshakes and ciphers b9023b0 (#19531) (CVE-2013-2275) Only allow report save from the node matching the certname Josh Cooper (7): f63ed48 Fix module tool acceptance test c42e608 Run openssl from windows when trying to downgrade master 8d199b2 Remove unnecessary rubygems require 3e493e1 Don't assume puppetbindir is defined 166bf79 Display SSL messages so we can match our regex 0328aaf Don't require openssl client to return 0 on failure 406725d Don't assume master supports SSLv2 Justin Stoller (6): cb607d9 Acceptance tests for CVEs 2013 (1640, 1652, 1653, 1654, 2274, 2275) 611b12d Separate tests for same CVEs into separate files f6e1987 We can ( and should ) use grep instead of grep -E 672af80 add quotes around paths for windows interop 28d80f0 remove tests that do not run on 3.1+ b87b719 run curl against the master on the master Moses Mendoza (1): 6c3dd98 Update PUPPETVERSION for 3.1.1 Nick Lewis (3): 940594b (#19393) Safely load YAML from the network 7da9559 Always read request body when using Rack 8f82131 Fix order-dependent test failure in network/authorization_spec Patrick Carlisle (3): eef6d38 (#19391) (CVE-2013-1652) Disallow use_node compiler parameter for remote requests f877cf5 (#19392) (CVE-2013-1653) Validate instances passed to indirector eb71909 (#19392) Don't validate key for certificate_status Pieter van de Bruggen (1): f6dbe99 Updating module tool acceptance tests with new expectations. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Enterprise 1.2.7 Available [ Security Release ]
Dear users of Puppet Enterprise 1.2.6 and earlier, Puppet Enterprise 1.2.7 is now available. This is a security release of Puppet Enterprise. Users of Puppet Enterprise 1.2.6 and earlier who are unable to upgrade to the current version of Puppet Enterprise, 2.7.2, are strongly encouraged to upgrade to this release. Puppet Enterprise 1.2.7 includes fixes to address CVE-2013-1640, CVE-2013-1652, CVE-2013-1654, CVE-2013-2274, and CVE-2013-2275. For more information, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-1640, http://puppetlabs.com/security/cve/cve-2013-1652, http://puppetlabs.com/security/cve/cve-2013-1654, http://puppetlabs.com/security/cve/cve-2013-2274, and http://puppetlabs.com/security/cve/cve-2013-2275. As a current Puppet Enterprise user, you can upgrade to this release as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. To download Puppet Enterprise 1.2.7 for your support platform, visit http://links.puppetlabs.com/puppet_enterprise_127. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. Thanks, Moses Mendoza Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet 2.6.18 Available [ Security Release ]
Puppet 2.6.18 is now available. 2.6.18 addresses several security vulnerabilities discovered in the 2.6.x line of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-1640, CVE-2013-1652, CVE-2013-1654, CVE-2013-2274, and CVE-2013-2275. All users of Puppet 2.6.17 and earlier who cannot upgrade to the current version of Puppet, 3.1.1, are strongly encouraged to upgrade to 2.6.18. For more information on these vulnerabilities, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-1640, http://puppetlabs.com/security/cve/cve-2013-1652, http://puppetlabs.com/security/cve/cve-2013-1654, http://puppetlabs.com/security/cve/cve-2013-2274, and http://puppetlabs.com/security/cve/cve-2013-2275. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.6.18.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 2.6.18: http://projects.puppetlabs.com/projects/puppet/ ## Changelog ## Andrew Parker (2): f45cd4b (#14093) Remove unsafe attributes from TemplateWrapper d9ad70a (#14093) Restore access to the filename in the template Daniel Pittman (2): 31dad7d (#8858) Refactor tests to use real HTTP objects 906ab92 (#8858) Explicitly set SSL peer verification mode. Jeff McCune (2): add9998 (#19151) Reject SSLv2 SSL handshakes and ciphers 16fce8e (#19531) (CVE-2013-2275) Only allow report save from the node matching the certname Josh Cooper (8): 7648de2 (#19391) Backport Request#remote? method 75a5f7e Run openssl from windows when trying to downgrade master e617728 Remove unnecessary rubygems require f07b761 Don't assume puppetbindir is defined a11a690 Display SSL messages so we can match our regex bb288aa Don't require openssl client to return 0 on failure f256c6d Don't assume master supports SSLv2 b166c4f (#19391) Find the catalog for the specified node name Justin Stoller (2): b01c728 Acceptance tests for CVEs 2013 (1640, 1652, 1653, 1654, 2274, 2275) e6b6124 Separate tests for same CVEs into separate files Matthaus Owens (1): 3ec5d5c Update CHANGELOG, lib/puppet.rb, conf/redhat/puppet.spec for 2.6.18 Nick Lewis (2): 66249d4 Always read request body when using Rack bdcf029 Fix order-dependent test failure in rest_authconfig_spec Patrick Carlisle (4): ccf2e4c (#19391) (CVE-2013-1652) Disallow use_node compiler parameter for remote requests 6a7bd25 (#19392) (CVE-2013-1653) Validate instances passed to indirector ac44d87 (#19392) (CVE-2013-1653) Validate indirection model in save handler d5c9a2c (#19392) (CVE-2013-1653) Fix acceptance test to catch unvalidated model on 2.6 -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet 2.7.21 Available [ Security Release ]
Puppet 2.7.21 is now available. 2.7.21 addresses several security vulnerabilities discovered in the 2.7.x line of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-1640, CVE-2013-1652, CVE-2013-1653, CVE-2013-1654, CVE-2013-1655 and CVE-2013-2275. All users of Puppet 2.7.20 and earlier who cannot upgrade to the current version of Puppet, 3.1.1, are strongly encouraged to upgrade to 2.7.21. For more information on these vulnerabilities, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-1640, http://puppetlabs.com/security/cve/cve-2013-1652, http://puppetlabs.com/security/cve/cve-2013-1653, http://puppetlabs.com/security/cve/cve-2013-1654, http://puppetlabs.com/security/cve/cve-2013-1655, and http://puppetlabs.com/security/cve/cve-2013-2275. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.21.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.21.msi RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/puppet-2.7.21.dmg Gems are available via rubygems at https://rubygems.org/downloads/puppet-2.7.21.gem or by using `gem install puppet --version=2.7.21` See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 2.7.21: http://projects.puppetlabs.com/projects/puppet/ ## Changelog ## Andrew Parker (2): cf6cf81 (#14093) Remove unsafe attributes from TemplateWrapper bd942ec (#14093) Restore access to the filename in the template Jeff McCune (2): be920ac (#19151) Reject SSLv2 SSL handshakes and ciphers 632e12d (#19531) (CVE-2013-2275) Only allow report save from the node matching the certname Josh Cooper (8): 7df884b Fix module tool acceptance test 0f4ac20 Run openssl from windows when trying to downgrade master 9cbfb9d Remove unnecessary rubygems require 70cdc63 Don't assume puppetbindir is defined 12728c0 Display SSL messages so we can match our regex 60eebed Don't require openssl client to return 0 on failure a1c4abd Don't assume master supports SSLv2 3ecd376 (#19391) Find the catalog for the specified node name Justin Stoller (2): 79b875e Acceptance tests for CVEs 2013 (1640, 1652, 1653, 1654, 2274, 2275) 7d62aa0 Separate tests for same CVEs into separate files Moses Mendoza (2): 4b0a7e2 Add missing 2.7.20 CHANGELOG entries 24d45dc Update CHANGELOG, PUPPETVERSION for 2.7.21 Nick Lewis (3): f2a3d5c (#19393) Safely load YAML from the network a3d3c95 Always read request body when using Rack 61109fa Fix order-dependent test failure in rest_authconfig_spec Patrick Carlisle (3): 516142e (#19391) (CVE-2013-1652) Disallow use_node compiler parameter for remote requests 0a7d61f (#19392) (CVE-2013-1653) Validate instances passed to indirector c240299 (#19392) Don't validate key for certificate_status Pieter van de Bruggen (1): 4a272ea Updating module tool acceptance tests with new expectations. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Facter 1.6.18-rc1 Available
Facter 1.6.18-rc1 is a maintenance release candidate in the 1.6.x series with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.18-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.18-rc1.dmg Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.18-rc1: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Fixes targeted at the final of this version in our bug tracker: http://projects.puppetlabs.com/versions/362 = ## Facter 1.6.18-rc1 Changelog ## = Jakob Borg (1): bf19fb3 (#15306) Read /proc/self/status in binary mode Jeff McCune (6): 7522fde Whitespace only reflow of README b8f6abf (maint) Add Travis CI support to active branches 51de32a Fix Travis CI failures on virtualbox fbf2893 (maint) Update gem source in Gemfile aeb1aa2 (maint) Add Ruby 2.0.0 to Travis build matrix 0710181 (maint) Fix failing manufacturer spec on Solaris 10 Matthaus Owens (2): 18ba6f3 (maint) Remove rc_mocks from build_defaults 871342f (maint) Add f18 mocks to build_defaults Moses Mendoza (3): 11a4143 [packaging] Remove natty from the deb pkg list, its EOL b07bcd5 [packaging] Update mocks for rpmbuilder mock format 11e9d52 Update lib/facter/version.rb for 1.6.18-rc1 Patrick Carlisle (2): a79451a Add missing require for macaddress 7d25751 Call correct function on IP in NetMask Toby Hsieh (2): 2a6faff (#18308) Use argv in Facter::Application.parse cf3e02b Add tests for Facter::Application.parse scepticulous (1): 891a148 (#13396) Unify ifconfig usage and lookup ifconfig path to fix support for recent net-tools -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Issue when istalling puppet-server in RHEL 6.
Strange. How about the output of: python -c 'import yum ; conf = yum.YumBase().conf ; print conf.yumvar["releasever"] ; print conf.distroverpkg' In a sane world this will print "6" and "redhat-release" (and the correct package would have installed originally). On Wed, Feb 20, 2013 at 10:51 PM, DreamBig wrote: > cat /etc/redhat-release > Red Hat Enterprise Linux Server release 6.2 (Santiago) > > > On Feb 19, 11:53 pm, Moses Mendoza wrote: >> On Tue, Feb 19, 2013 at 2:38 AM,DreamBig wrote: >> > Hi , >> >> > Following is the issue: >> >> > puppet.repo: >> >> > [puppetlabs] >> > name=Puppet Labs Packages >> > baseurl=http://yum.puppetlabs.com/el/$releasever/products/$basearch/ >> > enabled=1 >> > gpgcheck=1 >> > gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs >> >> > uname -a >> >> > Linux rniyer-linux 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST >> > 2011 x86_64 x86_64 x86_64 GNU/Linux >> >> > $ yum install puppet-server >> > Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, >> > subscription-manager >> > Updating certificate-based repositories. >> > puppetlabs >> > | 1.9 kB 00:00 >> > Not using downloaded repomd.xml because it is older than what we have: >> > Current : Thu Feb 14 12:17:53 2013 >> > Downloaded: Thu Feb 14 12:17:10 2013 >> > Setting up Install Process >> > Resolving Dependencies >> > --> Running transaction check >> > ---> Package puppet-server.noarch 0:3.1.0-1.el5 will be installed >> > --> Processing Dependency: puppet = 3.1.0-1.el5 for package: puppet- >> > server-3.1.0-1.el5.noarch >> > --> Running transaction check >> > ---> Package puppet.noarch 0:3.1.0-1.el5 will be installed >> > --> Processing Dependency: ruby-augeas for package: >> > puppet-3.1.0-1.el5.noarch >> > --> Processing Dependency: ruby-shadow for package: >> > puppet-3.1.0-1.el5.noarch >> > --> Running transaction check >> > ---> Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed >> > ---> Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed >> > --> Finished Dependency Resolution >> >> > Dependencies Resolved >> >> > = >> > Package >> > Arch >> > Version >> > RepositorySize >> > = >> > Installing: >> > puppet-server >> > noarch >> > 3.1.0-1.el5 >> > puppetlabs23 k >> > Installing for dependencies: >> > puppet >> > noarch >> > 3.1.0-1.el5 >> > puppetlabs 957 k >> > ruby-augeas >> > x86_64 >> > 0.4.1-1.el6 >> > aegisco 21 k >> > ruby-shadow >> > x86_64 >> > 1.4.1-13.el6 >> > aegisco 11 k >> >> > Transaction Summary >> > = >> > Install 4 Package(s) >> >> > Total size: 1.0 M >> > Total download size: 980 k >> > Installed size: 2.8 M >> > Is this ok [y/N]: >> >> > If you notice, it is picking the version 3.1.0-1.el5 when it should be >> > picking 3.1.0-1.el6 >> >> > How can I install using rpm instead of yum? >> >> Your issue is pointing to an oddity in your yum config. The >> puppet.repo file is using $releasever to determine the correct repo >> path. $releasever is determined by yum by checking the version of the >> package that provides `redhat-release`, unless you've overridden it in >> yum.conf. In your case, yum appears to think you're on an el 5 box. >> What distro/version are you running? What are the contents of >> /etc/redhat-release ? >> >> >> >> >> >> >> >> >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Puppet Users" group. >> > To u
Re: [Puppet Users] Issue when istalling puppet-server in RHEL 6.
On Tue, Feb 19, 2013 at 2:38 AM, DreamBig wrote: > Hi , > > Following is the issue: > > puppet.repo: > > [puppetlabs] > name=Puppet Labs Packages > baseurl=http://yum.puppetlabs.com/el/$releasever/products/$basearch/ > enabled=1 > gpgcheck=1 > gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs > > uname -a > > Linux rniyer-linux 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST > 2011 x86_64 x86_64 x86_64 GNU/Linux > > $ yum install puppet-server > Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, > subscription-manager > Updating certificate-based repositories. > puppetlabs > | 1.9 kB 00:00 > Not using downloaded repomd.xml because it is older than what we have: > Current : Thu Feb 14 12:17:53 2013 > Downloaded: Thu Feb 14 12:17:10 2013 > Setting up Install Process > Resolving Dependencies > --> Running transaction check > ---> Package puppet-server.noarch 0:3.1.0-1.el5 will be installed > --> Processing Dependency: puppet = 3.1.0-1.el5 for package: puppet- > server-3.1.0-1.el5.noarch > --> Running transaction check > ---> Package puppet.noarch 0:3.1.0-1.el5 will be installed > --> Processing Dependency: ruby-augeas for package: > puppet-3.1.0-1.el5.noarch > --> Processing Dependency: ruby-shadow for package: > puppet-3.1.0-1.el5.noarch > --> Running transaction check > ---> Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed > ---> Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed > --> Finished Dependency Resolution > > Dependencies Resolved > > = > Package > Arch > Version > RepositorySize > = > Installing: > puppet-server > noarch > 3.1.0-1.el5 > puppetlabs23 k > Installing for dependencies: > puppet > noarch > 3.1.0-1.el5 > puppetlabs 957 k > ruby-augeas > x86_64 > 0.4.1-1.el6 > aegisco 21 k > ruby-shadow > x86_64 > 1.4.1-13.el6 > aegisco 11 k > > Transaction Summary > = > Install 4 Package(s) > > Total size: 1.0 M > Total download size: 980 k > Installed size: 2.8 M > Is this ok [y/N]: > > If you notice, it is picking the version 3.1.0-1.el5 when it should be > picking 3.1.0-1.el6 > > How can I install using rpm instead of yum? Your issue is pointing to an oddity in your yum config. The puppet.repo file is using $releasever to determine the correct repo path. $releasever is determined by yum by checking the version of the package that provides `redhat-release`, unless you've overridden it in yum.conf. In your case, yum appears to think you're on an el 5 box. What distro/version are you running? What are the contents of /etc/redhat-release ? > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Recent Security Vulnerabilities
All, In the last few weeks, several serious security vulnerabilities have been disclosed in components of Ruby on Rails, Rack, the JSON rubygem, Ruby 1.9, and certain cryptographic protocols used in OpenSSL. These include CVE-2013-0276, CVE-2013-0277, CVE-2013-0263, CVE-2013-0269, CVE-2013-0169, CVE-2012-6496, CVE-2012-6497, CVE-2013-0155, and CVE-2013-0156, and the list goes on. CVE details on all of these vulnerabilities can be found at the Mitre website, using the CVE number as the search query, e.g.: http://cve.mitre.org/cgi-bin/cvename.cgi?name= Puppet Labs has provided or is in the process of generating hotfixes and patch releases for our products that are affected by these vulnerabilities, which we strongly urge all users to update to as soon as possible. All security announcements for Puppet software are sent to the Puppet-Announce mailing list. To follow security releases and our other software announcements, join at groups.google.com/group/puppet-announce. This is just a friendly, if not urgent, reminder to all the Puppet users that if you are using Ruby on Rails, Rack, JSON, and/or OpenSSL outside of our products or in tandem with them in some way (e.g. Puppet ActiveRecord-based storeconfigs), it is critical to update your installations to the latest patch versions of this software. These recent CVEs are no trifle. They are serious vulnerabilities with massive potential attack payloads, including arbitrary code execution, SQL injection, and the like (e.g. "all your hosts are belong to me"). Regards, Moses Mendoza Release Engineering, Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet Enterprise hotfixes for CVE-2013-0277, CVE-2013-0263, CVE-2013-0269, and CVE-2013-0169.
Security vulnerabilities have been disclosed in Ruby on Rails, Rack, the JSON rubygem, and certain cryptographic protocols used in OpenSSL, assigned CVEs CVE-2013-0277, CVE-2013-0263, CVE-2013-0269 and CVE-2013-0169, respectively. These vulnerabilities affect Puppet Enterprise. CVE-2013-0277 affects the 2.3 and 3.0 series of Rails. The vulnerability allows an attacker to cause deserialization of arbitrary YAML. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0277. CVE-2013-0263 affects session cookie handling in Rack. The vulnerability exposes Rack to privilege escalation and arbitrary code execution. CVE details can be found at http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0263. CVE-2013-0269 affects all versions of the JSON gem. This vulnerability exposes Ruby on Rails to SQL injection and denial of service attacks. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0269. CVE-2013-0169 affects the TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in various cryptographic libraries and products, including OpenSSL, OpenJDK, PolarSSL. This vulnerability allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks. This CVE affects Puppet Enterprise Solaris and Windows agents only, as the agent packages for these platforms ship with a built-in version of OpenSSL that is vulnerable. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0169. Puppet Labs has generated security hotfixes patching the vulnerability for the latest in the 1.x series and 2.x series of Puppet Enterprise. These can be downloaded from the Puppet Labs security pages for these events: http://puppetlabs.com/security/cve/cve-2013-0277 http://puppetlabs.com/security/cve/cve-2013-0263 http://puppetlabs.com/security/cve/cve-2013-0269 http://puppetlabs.com/security/cve/cve-2013-0169 Note: in the case of the pe-puppet-dashboard package, the updated package contains security fixes for CVEs CVE-2013-0277, CVE-2013- 263, and CVE-2013-0269. For consistency the package appears in all three CVE folders, but only one installation of pe-puppet-dashboard is necessary. These security fixes will also be included in forthcoming patch releases of Puppet Enterprise, versions 1.2.7 and 2.7.2. If you have any questions or comments, please get in touch with Puppet Labs Support. We always want your feedback! Regards, Moses Mendoza Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Dashboard 1.2.22 Available [ security release ]
This release of Puppet Dashboard addresses CVE-2013-0277 and CVE-2013-0269. These are vulnerabilities that affect Ruby on Rails, specifically around YAML serialization and JSON handling. They expose vulnerable systems to SQL Injection, Denial of Service Attacks, and arbitrary YAML deserialization. Additionally, CVE-2013-0276 and CVE-2013-0263 affect vendored components of Puppet Dashboard, but by default Puppet Dashboard does not interact with them in a way that exposes it to these vulnerabilities. Nevertheless, this release of Puppet Dashboard addresses these CVEs as well. Detailed information on the CVEs can be found at these URLs: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0269 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0277 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0276 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0263 Downloads RPM packages for are available at https://yum.puppetlabs.com/el or /fedora Debian packages are available at https://apt.puppetlabs.com Source can be downloaded from https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.22.tar.gz, along with the accompanying signature file, https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.22.tar.gz.asc. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Changelog Nick Lewis (4): efab99d Upgrade to Rails 2.3.17 d2ae98f Upgrade to rack 1.1.6 90f2ca6 Upgrade json_pure to 1.5.5 2128ed8 Fix failing test due to new HTML-escaping rules -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dashboard permission issue
On Tue, Feb 5, 2013 at 1:15 AM, wrote: > I'm having trouble getting puppet dashboard (1.2.21) to run on apache. > > i installed puppetmaster-passenger and puppet-dashboard package. It didn't > create user puppet-dashboard automatically as stated in the installation > guide, > so i created one manually and chowned all files under /puppet-dashboard. > when testing with webrick everything works fine (as root). > when i try with other users this is what happens: > > root@puppetmaster:/usr/share/puppet-dashboard/script# sudo -u > puppet-dashboard ./server -e production > => Booting WEBrick > => Rails 2.3.14 application starting on http://0.0.0.0:3000 > ./../config/../vendor/rails/railties/lib/initializer.rb:926:in `read': > Permission denied - /usr/share/puppet-dashboard/config/database.yml > (Errno::EACCES) > from ./../config/../vendor/rails/railties/lib/initializer.rb:926:in > `database_configuration' > from ./../config/../vendor/rails/railties/lib/initializer.rb:437:in > `initialize_database' > from ./../config/../vendor/rails/railties/lib/initializer.rb:141:in > `process' > from ./../config/../vendor/rails/railties/lib/initializer.rb:113:in `send' > from ./../config/../vendor/rails/railties/lib/initializer.rb:113:in `run' > from /usr/share/puppet-dashboard/config/environment.rb:14 > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require' > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' > from > /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in > `require' > from > /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in > `new_constants_in' > from > /usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in > `require' > from > /usr/share/puppet-dashboard/vendor/rails/railties/lib/commands/server.rb:84 > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require' > from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' > from ./server:3 > > When running with apache, passneger gives the same error: > Permission denied - /usr/share/puppet-dashboard/config/database.yml > Application root: /usr/share/puppet-dashboard > > I tried changing ownerships, giving 777 rights on files etc.. > First run with webrick might have been as root. Could this be an issue? If > so, is it fixable or am i due for a reinstallation? > > Thanks a million for any help on this!! > /usr/share/puppet-dashboard/config/database.yml is actually a symlink to /etc/puppet-dashboard/config/database.yml, and the same with settings.yml, respectively. Check if the permissions in /etc/puppet-dashboard allow read by the puppet-dashboard user. You're correct about the package not creating the user, this is a known issue that needs to get fixed - http://projects.puppetlabs.com/issues/18135. > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problems with PuppetLabs Yum Repo
Hey Dan, I couldn't replicate the issue, I was able to install the el5 package from yum.puppetlabs.com without issue. Perhaps you have a stale metadata issue? Moses -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Dashboard upgrade from 1.2.17 to 1.2.20 failed on Debian
On Friday, January 18, 2013, Julien Cornuwel wrote: > Hi, > > My Puppet Dashboard is running on Debian stable, installed from puppetlabs > repositories. > The last upgrade completely broke down. See below for the output: > > # aptitude safe-upgrade > The following packages will be upgraded: > libactionmailer-ruby1.8 libactionpack-ruby1.8 libactiverecord-ruby1.8 > libactiveresource-ruby1.8 libactivesupport-ruby1.8 puppet-dashboard rails > rails-ruby1.8 > 8 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 6,393 kB of archives. After unpacking 115 kB will be freed. > Do you want to continue? [Y/n/?] > Get:1 http://security.debian.org/ squeeze/updates/main rails-ruby1.8 all > 2.3.5-1.2+squeeze5 [223 kB] > Get:2 http://security.debian.org/ squeeze/updates/main > libactiverecord-ruby1.8 all 2.3.5-1.2+squeeze5 [265 kB] > Get:3 http://security.debian.org/ squeeze/updates/main > libactivesupport-ruby1.8 all 2.3.5-1.2+squeeze5 [256 kB] > Get:4 http://security.debian.org/ squeeze/updates/main > libactionmailer-ruby1.8 all 2.3.5-1.2+squeeze5 [32.1 kB] > Get:5 http://security.debian.org/ squeeze/updates/main > libactionpack-ruby1.8 all 2.3.5-1.2+squeeze5 [321 kB] > Get:6 http://security.debian.org/ squeeze/updates/main > libactiveresource-ruby1.8 all 2.3.5-1.2+squeeze5 [37.2 kB] > Get:7 http://security.debian.org/ squeeze/updates/main rails all > 2.3.5-1.2+squeeze5 [12.3 kB] > Get:8 http://apt.puppetlabs.com/ squeeze/main puppet-dashboard all > 1.2.20-1puppetlabs1 [5,246 kB] > > Fetched 6,393 kB in 11s (564 kB/s) > > > Reading changelogs... Done > (Reading database ... 52761 files and directories currently installed.) > Preparing to replace puppet-dashboard 1.2.17-1puppetlabs1 (using > .../puppet-dashboard_1.2.20-1puppetlabs1_all.deb) ... > Stopping Puppet Dashboard Workers:E: Sub-process /usr/bin/dpkg exited > unexpectedly > A package failed to install. Trying to recover: > dpkg: error processing puppet-dashboard (--configure): > Package is in a very bad inconsistent state - you should > reinstall it before attempting configuration. > Errors were encountered while processing: > puppet-dashboard > > # apt-get install puppet-dashboard --reinstall > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages will be upgraded: > puppet-dashboard > 1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. > 1 not fully installed or removed. > Need to get 0 B/5,246 kB of archives. > After this operation, 115 kB disk space will be freed. > Reading changelogs... Done > Selecting previously deselected package puppet-dashboard. > (Reading database ... 52761 files and directories currently installed.) > Preparing to replace puppet-dashboard 1.2.17-1puppetlabs1 (using > .../puppet-dashboard_1.2.20-1puppetlabs1_all.deb) ... > Stopping Puppet Dashboard Workers:E: Sub-process /usr/bin/dpkg exited > unexpectedly > It appears the dashboard workers may have fails to stop during the package upgrade. Could you try stopping the dashboard workers and then retry package upgrade? This should not normally be necessary, the upgrade handling in the package should have taken care of this, so we'll take a look at why this may have failed. > > # apt-get remove puppet-dashboard > E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to > correct the problem. > > # dpkg --configure -a > dpkg: error processing puppet-dashboard (--configure): > Package is in a very bad inconsistent state - you should > reinstall it before attempting configuration. > Errors were encountered while processing: > puppet-dashboard > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/giSi5xXYhngJ. > To post to this group, send email to > puppet-users@googlegroups.com 'puppet-users@googlegroups.com');> > . > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com 'puppet-users%2bunsubscr...@googlegroups.com');>. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet Dashboard 1.2.20 Available
Puppet Dashboard 1.2.20 is now available! This release of Puppet Dashboard addresses an issue in the 1.2.19 packages where the version link still reads "1.2.18". This release also changes the target of the link to the Github Puppet Dashboard repo from the CHANGELOG file to the list of commits in the packaged version. Downloads RPM packages for are available at https://yum.puppetlabs.com/el or /fedora Debian packages are available at https://apt.puppetlabs.com Source can be downloaded from https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.20.tar.gz, along with the accompanying signature file, https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.20.tar.gz.asc. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet 1.2.20 Changelog ======== Moses Mendoza (2): 25b5bca Remove CHANGELOG file, update version link e937353 Update VERSION for 1.2.20 release -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Announce: Puppet Dashboard 1.2.19 Available
Hi Ellison, You're right! Thanks for pointing that out. I failed to update the VERSION file at the top of dashboard, which gets sourced for that link. Otherwise, this is indeed 1.2.19:) Moses On Tue, Jan 15, 2013 at 6:04 PM, Ellison Marks wrote: > Just updated and noticed that the version number at the top of the page in > dashboard didn't bump, and it still lists 1.2.18 in > /usr/share/puppet-dashboard/VERSION. This is on CentOS 6 from yum. > > > On Tuesday, January 15, 2013 4:59:45 PM UTC-8, Moses Mendoza wrote: >> >> Puppet Dashboard 1.2.19 is now available. >> >> This release of Puppet Dashboard addresses CVE-2013-0155. All users >> are strongly encouraged to update when possible. >> >> This vulnerability exposes ActiveRecord to unsafe query generation. >> >> More information on the vulnerability can be found here: >> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0155, and in >> this post: >> https://groups.google.com/group/rubyonrails-security/browse_thread/thread/73b8d3f8478df5e2 >> >> Downloads >> >> >> RPM packages for are available at https://yum.puppetlabs.com/el or /fedora >> >> Debian packages are available at https://apt.puppetlabs.com >> >> Source can be downloaded from >> https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.19.tar.gz, >> along with the accompanying signature file, >> >> https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.19.tar.gz.asc. >> >> See the Verifying Puppet Download section at: >> http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet >> >> 1.2.19 Security Fixes >> >> Ernie Miller (1): >> 04c1dba Fix for CVE-2013-0155 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/r7xJE--NIDIJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet Dashboard 1.2.19 Available
Puppet Dashboard 1.2.19 is now available. This release of Puppet Dashboard addresses CVE-2013-0155. All users are strongly encouraged to update when possible. This vulnerability exposes ActiveRecord to unsafe query generation. More information on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0155, and in this post: https://groups.google.com/group/rubyonrails-security/browse_thread/thread/73b8d3f8478df5e2 Downloads RPM packages for are available at https://yum.puppetlabs.com/el or /fedora Debian packages are available at https://apt.puppetlabs.com Source can be downloaded from https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.19.tar.gz, along with the accompanying signature file, https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.19.tar.gz.asc. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet 1.2.19 Security Fixes Ernie Miller (1): 04c1dba Fix for CVE-2013-0155 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Enterprise hotfixes for ActiveRecord vulnerability [ CVE-2013-0155 ]
Good day, A security vulnerability has been disclosed in Ruby on Rails, specifically in all versions of ActiveRecord, assigned CVE-2013-0155. An earlier Rails advisory of this vulnerability mistakenly stated that the version of ActiveRecord used in Puppet Enterprise was not affected. The vulnerability exposes ActiveRecord to unsafe SQL query generation. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0155 Additional detailed information can be found in the following post: https://groups.google.com/group/rubyonrails-security/browse_thread/thread/73b8d3f8478df5e2 Puppet Labs has generated security hotfixes patching the vulnerability for the latest in the 1.x series and 2.x series of Puppet Enterprise. These can be downloaded from the Puppet Labs security page: http://puppetlabs.com/security/cve/cve-2013-0155/. These security fixes will also be included in the forthcoming patch releases of Puppet Enterprise, versions 1.2.6 (security only) and 2.7.1 (security and bug fix). If you have any questions or comments, please get in touch with Puppet Labs Support. We always want your feedback! Regards, Moses Mendoza Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: PuppetDB 1.1.0-rc5 Available
PuppetDB 1.1.0-rc5 is now available for download. 1.1.0-rc5 specifically addresses a regression in Debian packaging of PuppetDB. RPM packages are unchanged since 1.1.0-rc4. # Downloads == Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Announce: PuppetDB 1.1.0-rc4 now available
On Thu, Jan 10, 2013 at 7:27 AM, Eric Kissinger wrote: > > > The puppetdb-1.1.0-0.1rc4.el6.noarch.rpm package seems to have an error when > unpacking the puppetdb.jar. > > This is the output: > > > Downloading Packages: > puppetdb-1.1.0-0.1rc4.el6.noarch.rpm > | 14 MB 00:00 > Running rpm_check_debug > Running Transaction Test > Transaction Test Succeeded > Running Transaction > Updating : puppetdb-1.1.0-0.1rc4.el6.noarch >1/2 > Error unpacking rpm package puppetdb-1.1.0-0.1rc4.el6.noarch > warning: /etc/puppetdb/conf.d/config.ini created as > /etc/puppetdb/conf.d/config.ini.rpmnew > error: unpacking of archive failed on file > /usr/share/puppetdb/puppetdb.jar;50eed3a6: cpio: read Hi Eric, I'm having a hard time replicating your issue. On my centos 6 vm, I can do a clean install and also upgrade from puppetdb 1.0.5 without issue. Also of note, your log shows a file size of 14 MB, but puppetdb is more like 16 MB, which perhaps could indicate some corruption somewhere. E.g., from my install output: Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 16 M puppetdb-1.1.0-0.1rc4.el6.noarch.rpm | 16 MB 00:30 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : puppetdb-1.1.0-0.1rc4.el6.noarch 1/1 Certificate was added to keystore Verifying : puppetdb-1.1.0-0.1rc4.el6.noarch 1/1 Installed: puppetdb.noarch 0:1.1.0-0.1rc4.el6 Complete! Perhaps something went awry during your repo metadata gathering? Maybe try `yum clean metadata`? and installing again? In case its a packaging issue, what version of puppetdb are you upgrading from, and what OS are you installing onto? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: PuppetDB 1.1.0-rc4 now available
PuppetDB 1.1.0-rc4 is now available for download! This is a feature and bug-fix release candidate of PuppetDB. Note: Release candidates 1-3 were never pushed to repositories due issues in packaging that were discovered prior to release. RC-4 is the first packaged release candidate for PuppetDB 1.1.0. # Downloads == Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.3 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/ puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # Changelog 1.1.0-rc4 = Many thanks to the following people who contributed patches to this release: * Chris Price * Deepak Giridharagopal * Jeff Blaine * Ken Barber * Kushal Pisavadia * Matthaus Litteken * Michael Stahnke * Moses Mendoza * Nick Lewis * Pierre-Yves Ritschard Notable features: * Enhanced query API A substantially improved version 2 of the HTTP query API has been added. This is located under the /v2 route. Detailed documentation on all the available routes and query language can be found in the API documentation, but here are a few of the noteworthy improvements: * Query based on regular expressions Regular expressions are now supported against most fields when querying against resources, facts, and nodes, using the ~ operator. This makes it easy to, for instance, find *all* IP addresses for a node, or apply a query to some set of nodes. * More node information Queries against the /v2/nodes endpoint now return objects, rather than simply a list of node names. These are effectively the same as what was previously returned by the /status endpoint, containing the node name, its deactivation time, as well as the timestamps of its latest catalog, facts, and report. * Full fact query The /v2/facts endpoint supports the same type of query language available when querying resources, where previously it could only be used to retrieve the set of facts for a given node. This makes it easy to find the value of some fact for all nodes, or to do more complex queries. * Subqueries Queries can now contain subqueries through the `select-resources` and `select-facts` operators. These operators perform queries equivalent to using the /v2/resources and /v2/facts routes, respectively. The information returned from them can then be correlated, to perform complex queries such as "fetch the IP address of all nodes with Class[apache]", or "fetch the operatingsystemrelease of all Debian nodes". These operators can also be nested and correlated on any field, to answer virtually any question in a single query. * Friendlier, RESTful query routes In addition to the standard query language, there are also now more friendly, "RESTful" query routes. For instance, /v2/nodes/ foo.example.com will return information about the node foo.example.com. Similarly, /v2/facts/operatingsystem will return the operatingsystem of every node, or /v2/nodes/foo.example.com/operatingsystem can be used to just find the operatingsystem of foo.example.com. The same sort of routes are available for resources as well. /v2/resources/User will return every User resource, /v2/resources/User/joe will return every instance of the User[joe] resource, and /v2/nodes/foo.example.com/Package will return every Package resource on foo.example.com. These routes can also have a query parameter supplied, to further query against their results, as with the standard query API. * Improved catalog storage performance Some improvements have been made to the way catalog hashes are computed for deduplication, resulting in somewhat faster catalog storage, and a significant decrease in the amount of time taken to store the first catalog received after startup. * Experimental report submission and storage The 'puppetdb' report processor is now available, which can be used (alongside any other reports) to submit reports to PuppetDB for storage. This feature is considered experimental, which means the query API may change significantly in the future. The ability to query reports is currently limited and experimental, meaning it is accessed via /experimental/reports rather than /v2/reports. C
[Puppet Users] Puppet Enterprise hotfixes for ActiveRecord vulnerability [ CVE-2012-5664 ]
Good day, A security vulnerability has been discovered in Ruby on Rails, specifically in all versions of ActiveRecord. It is assigned CVE-2012-5664. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. CVE details on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 Additional detailed information can be found in the following post: https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/DCNTNp_qjFM Puppet Labs has generated security hotfixes patching the vulnerability for the latest in the 1.x series and 2.x series of Puppet Enterprise. These can be downloaded from the Puppet Labs security page: http://puppetlabs.com/security/cve/cve-2012-5664/. These security fixes will also be included in the forthcoming patch releases of Puppet Enterprise, versions 1.2.6 (security only) and 2.7.1 (security and bug fix). If you have any questions or comments, please get in touch with Puppet Labs Support. We always want your feedback! Regards, Moses Mendoza Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Rails ActiveRecord vulnerability & Puppet legacy storeconfigs [ security ]
Good day, A security vulnerability has been discovered in Ruby on Rails, specifically in all versions of ActiveRecord. It is assigned CVE-2012-5664. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. CVE details can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 If you currently use Puppet's ActiveRecord-based storeconfigs, you will mostly likely want to update your ActiveRecord version or patch your version to address the risk (or even better, use PuppetDB, a drop-in replacement: http://docs.puppetlabs.com/puppetdb/). See the following post for more information on the vulnerability: https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/DCNTNp_qjFM Regards, Moses Mendoza Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet-Dashboard 1.2.17 Available [ Security Release ]
Puppet Dashboard 1.2.17 is now available. This release of Puppet Dashboard addresses CVE 2012-5664. All users are strongly encouraged to update when possible. CVE-2012-5664 affects Ruby on Rails, specifically in all versions of ActiveRecord. The vulnerability exposes ActiveRecord to arbitrary SQL Injection. More information on the vulnerability can be found here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664 Downloads RPM packages for are available at https://yum.puppetlabs.com/el or /fedora Debian packages are available at https://apt.puppetlabs.com Source can be downloaded from https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.17.tar.gz, along with the accompanying signature file, https://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.2.17.tar.gz.asc . See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet 1.2.17 Security Fixes Aaron Stone (1): 5b7bdca Patch for CVE-2012-5664: options hashes should only be extracted if there are extra parameters -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet Dashboard 1.2.16 Available!
Puppet Dashboard 1.2.16 is a maintenance release of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This is the first release of Puppet Dashboard with Aaron Stone (sodabrew on github) having commit rights. He has already helped shepherd many pull requests from submission to merge. Thanks Aaron! This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.16.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.16: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html Contributors: Aaron Stone, Glenn Poston, Matthaus Owens = ## Puppet Dashboard 1.2.16 Release Notes ## = Add listclasses, delclass to nodegroup rake tasks Previously once a class had been added to a nodegroup, there was no way of removing it, short of deleting the group and adding the desired classes back. However, if you wanted to list the classes in that group, you were still out of luck, because there was no listclasses task for the nodegroup namespace. This commit adds both of those tasks to the nodegroup namespace. listclasses lists the classes assigned to a nodegroup and delclass removes a class from a nodegroup, if such a class exists in the nodegroup. Add tabs to filter reports based on status - supporting named_scopes in report model - supporting routes - supporting controller actions == ## Puppet Dashboard 1.2.16 Changelog ## == Aaron Stone (7): ba35090 'verb'! do |success, failure| is only for verbs create, update, destroy; everything else must use 'verb'! do |format|. 9c8626b Call Metric.new instead of metrics.new, which caused a duplication of all metrics. c77afe9 Report.create_from_yaml does several retries, so mock with 'stubs' instead of 'expects' to handle any number of retry calls. 3784739 Revert "(maint) fix failing tests" 9d162d3 Fix tests after merging 0aadf8876d from master. 6088c93 Begin the changelog for the next release 138922c Update changelog with today's merges. Glenn Poston (2): d052a9c added tabs to filter reports based on status - supporting named_scopes in report model - supporting routes - supporting controller actions 5635147 added tabs to filter reports based on status - supporting named_scopes in report model - supporting routes - supporting controller actions Matthaus Owens (6): 2c7c96a Retab rescue block to line up with other flow control 4445672 Add listclasses, delclass to nodegroup rake tasks f9d6d72 Style tweaks to new tasks. Better tabbing, remove escaped single quotes. 310fa54 Add quantal to default cows list. e955daf Revert "Merge pull request #112 from gposton/master" fcdff5d Update CHANGELOG, VERSION for 1.2.16-rc1 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 3.0.2 Available!
Puppet 3.0.2 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.2 version in our issue tracter at: https://projects.puppetlabs.com/versions/337 Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.0.2.tar.gz RPMs are available at https://yum.puppetlabs.com Debs are available at https://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.2.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.0.2.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.0.2.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.2: https://projects.puppetlabs.com/projects/puppet/ ## Puppet 3.0.2 Contributors ## Andrew Parker, Dan Bode, Daniel Pittman, Dominic Cleal, Eric Sorenson, Gary Larizza, Henrik Lindberg, Hunter Haugen, Jeff McCune, Josh Cooper, Linus Sellberg, Lubomir Rintel, Matt Callaway, Matthaus Owens, Michael Hall, Michael Stahnke, Moses Mendoza, Neil Hemingway, Nick Fagerlund, Patrick Carlisle, Patrick Mooney, Sean E. Millichamp, Todd Zullinger ## Puppet 3.0.2 Release Notes ## #10963 Collector overrides should work in Ruby 1.9 Increase arity of child_of? meta_def to 1 child_of? defined for Puppet::Resource::Type objects has an arity of 1, but the meta_def of the same function created by Puppet::Parser::Collector objects has an arity of 0. This throws errors when the meta_def method is called with arguments. This commit matches the arity so that this error will not be present. #15929, #17624 Handle malformed plists Previously, if launchd encountered a plist that did NOT have a 'label' key, or a malformed plist that plutil couldn't read, Puppet would throw a stacktrace or log a nebulous error that looked like: `Error: Could not run: No resource and no name in property hash in launchd instance` That was not ideal. This commit will catch the situation where a plist is missing a 'label' key Puppet is skipping the plist. It will also catch the case the where a plist is malformed and plutil cannot read it. With either condition, the commit adds code that logs a Puppet.warning and skips the malformed plist gracefully. #18046 Enable rubygems support Previously, puppet used to require rubygems, but this broke environments that didn't use rubygems. The decision to require rubygems was moved out of puppet and into the code that loads puppet. This was done for daemon.bat, but not for the other scripts, e.g. puppet.bat. This commit enables rubygems support in the environment.bat file which all of the other bat files source. #18047 Revert change to user confdir In 3.0, the default user confdir (and vardir) was changed from ~/.puppet to the Dir::LOCAL_APPDATA/PuppetLabs. However, when puppet is run as a non-administrator, puppet will attempt to create its confdir, e.g. C:\Users\albert\AppData\Local\PuppetLabs\puppet, and fail because the parent PuppetLabs directory doesn't exist. This wasn't an issue in 2.7.x, because the confdir was ~/.puppet, so the parent directory always existed. This commit restores the previous behavior for non-administrators. No changes are required for administrators, because the MSI installer creates the necessary directories within COMMON_APPDATA. = ## Puppet 3.0.2 Changelog ## = Andrew Parker (16): c6b8e7f (Maint) Update Gemfile for use in Puppet Labs Jenkins 13ab956 (#16791) Revert "Merge branch 'perf/2.7.x/backport-activesupport-hook-disabling' of https://github.com/daniel-pittman/puppet into 2.7.x" 1e5baee (#16791) Revert "Maint: Fix intermittently failing spec test" 3cda4f4 (#16791) Revert "Merge branch 'feature/2.7.x/json-terminus-backport' of https://github.com/daniel-pittman/puppet into 2.7.x" aba3c67 (#16791) Re-instate deprecated symbolize and symbolizehash! d892859 (#16791) Remove tests for unused behavior bd0caf5 (#17260) Warn when variables contain hyphens 5c61f32 (#17260) Include link to information about deprecation b5ed15b (#17458) Load 'puppet' at the right time d16d357 (#17458) Add acceptance test for executing external subcommands e8434b0 (#16178) Add test for behavior of false values in lookup 453249f (Maint) Require Hiera::Backend where it is used a0df02c (Maint) Remove duplication and mocking from tests 03f658f (#16178) Stop checking for :undefined ab7a88d (#16728) Unify handling of log coloring and prefi
[Puppet Users] Announce: PuppetDB 1.0.5 Available
PuppetDB 1.0.5 is now available for download! This is a bug-fix release of PuppetDB. # Downloads == Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.1 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # Changelog 1.0.5 = Many thanks to the following people who contributed patches to this release: * Chris Price * Deepak Giridharagopal Fixes: * Drop a large, unused index on catalog_resources(tags) This index was superseded by a GIN index on the same column, but the previous index was kept around by mistake. This should result in a space savings of 10-20%, as well as a possible very minor improvement in catalog insert performance. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Facter 1.6.17-rc1 Available
Facter 1.6.17-rc1 is a maintenance release candidate in the 1.6.x
branch with bug fixes.
Downloads are available at:
* Source: https://downloads.puppetlabs.com/facter/facter-1.6.17-rc1.tar.gz
RPMs are available at https://yum.puppetlabs.com/el or /fedora
Rubygem available at http://rubygems.org/gems/facter or by using
the --pre option to gem install.
Debs are available at https://apt.puppetlabs.com
Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.6.17-rc1.dmg
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads
Please report feedback via the Puppet Labs Redmine site, using a
affected version of 1.6.17-rc1:
http://projects.puppetlabs.com/projects/facter/
Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki
Fixes targeted at the final of this version in our bug tracker:
http://projects.puppetlabs.com/versions/359
## Facter 1.6.17-rc1 Changelog ##
Adrien Thebo (2):
e35acbb (#17840) Use enum_cpuinfo for x86 arch
e5ca916 (maint) Remove processor_spec duplicate stubbing
Alex Harvey (1):
b62b3f6 (#17487) Add support for HPUX NIC bonding in IP facts
Chris Barker (1):
3628533 (#15708) fixes facter file mappings for pkgbuild
Jared Curtis (2):
41909b7 (#15001) ifconfig regex will optionally match 'addr:'
ae34893 Test data for net-tools 1.60
Jeff McCune (4):
c0b123b (#16626) Exercise IP.get_interface_value("bond0","macaddress")
10a1380 (Maint) Add YARD doc for get_interface_value
656c5ae (#17925) Fix ec2_userdata: 404 Not Found Error
0e514b8 (#15001) Add spec examples for ipaddress fact
Jos Backus (1):
7bba9b2 (#16626) Fix handling of bonded Linux interfaces
Josh Cooper (1):
0b672ed (#17855) Rescue Timeout::Error
Matthaus Owens (2):
09ad0bb Remove fedora 15 mocks, as f15 is EOL.
5cfd683 Add quantal to default cows list.
Moses Mendoza (1):
d770aec Update lib/facter/version.rb for 1.6.17-rc1
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: PuppetDB 1.0.4 Available
PuppetDB 1.0.4 is now available for download! This is a bug-fix release of PuppetDB. Note: Puppet 1.0.3 was not officially released, as additional fixes came in between the time 1.0.3 was tagged and the time we were going to publish release artifacts. PuppetDB 1.0.4 includes all changes from the would-be 1.0.3. # Downloads == Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.1 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # Changelog(s) 1.0.4 = Many thanks to the following people who contributed patches to this release: * Chris Price Fixes: * (#16554) Fix postgres query for numeric comparisons This commit changes the regex that we are using for numeric comparisons in postgres to a format that is compatible with both 8.4 and 9.1. 1.0.3 = NOTE: This version was not officially released, as additional fixes came in between the time we tagged this and the time we were going to publish release artifacts. Many thanks to the following people who contributed patches to this release: * Deepak Giridharagopal * Nick Lewis * Chris Price Fixes: * (#17216) Fix problems with UTF-8 transcoding Certain 5 and 6 byte sequences were being incorrectly transcoded to UTF-8 on Ruby 1.8.x systems. We now do two separate passes, one with iconv and one with our hand-rolled transcoding algorithms. Better safe than sorry! * (#17498) Pretty-print JSON HTTP responses We now output more nicely-formatted JSON when using the PuppetDB HTTP API. * (#17397) DB pool setup fails with numeric username or password This bug happens during construction of the DB connection pool. If the username or password is numeric, when parsing the configuration file they're turned into numbers. When we go to actually create the pool, we get an error because we're passing in numbers when strings are expected. * (#17524) Better logging and response handling for version checks Errors when using the `version` endpoint are now caught, logged at a more appropriate log level, and a reasonable HTTP response code is returned to callers. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] delete home directory rescurively
On Sat, Nov 24, 2012 at 8:28 AM, bluethundr wrote:
> Is there a way using puppet to delete the home directories recursively of
> employees who have left the company?
Are your users managed by Puppet? If so, perhaps check out
`managehome` of the user type.
http://docs.puppetlabs.com/references/latest/type.html#user .
Depending on the capabilities of the provider for your system, setting
`managehome => true` will create/remove user home directories.
>
> So far I've tried:
>
>file { "/export/home/user":
> name => "$home_dir/user",
> ensure => 'absent'
> }
>
> I also tried
>
>
>
> file{'export/home/user':
> name => "$home_dir/user",
> purge => true,
> recurse => true,
> force => true,
> backup => false,
> }
>
> But neither worked. Is there a way to do this with puppet currently? All I
> could find in the googlesphere was how to create directories (and keep them
> clean) with puppet but not how to destroy them. Perhaps this would be TOO
> destructive a power for puppet to wield?
>
> Thanks
> Tim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/ffzGcfykLHIJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 2.7.20 Available
Puppet 2.7.20 is a maintenance release for Puppet in the 2.7.x series with bug fixes and backwards-compatible performance improvements back-ported from the 3.0.x series. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.20.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.20.msi RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/puppet-2.7.20.dmg Gems are available via rubygems at https://rubygems.org/downloads/puppet-2.7.20.gem or by using `gem install puppet --version=2.7.20` See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 2.7.20: http://projects.puppetlabs.com/projects/puppet/ To take a look at fixes targeted for this release, check out http://projects.puppetlabs.com/versions/307 ## Contributors ## Adrien Thebo, Andrew Parker, Ashley Penney, Branan Purvine-Riley, Dan Bode, Daniel Pittman, Dominic Cleal, Dustin J. Mitchell, Eric Sorenson, Eric Stonfer, Gleb Arshinov, James Turnbull, Jeff McCune, Jeff Weiss, Josh Cooper, Ken Barber, Ken Dreyer, Lee Lowder, Markus Roberts, Matthaus Owens, Michael Stahnke, Moses Mendoza, Neil Hemingway, Nick Fagerlund, Patrick Carlisle, Roman Barczyński, S. Zachariah Sprackett, Sean E. Millichamp, Stefan Schulte, Todd Zullinger ## Special notes about 2.7.20 ## Puppet 2.7.20 address http://projects.puppetlabs.com/issues/15560, which means if you had specifically enabled `managehome => true` for user resources expecting it not to work on Windows, be aware that it **works now** for both creation with `ensure => present` AND deletion with `ensure => absent`. Previously deleted users will not have their orphaned home directories removed, however. Puppet 2.7.20 also addresses concerns regarding a change introduced in Puppet 2.7.16, "b26699a (#10146) `-` is not legal in variable names.", which disallowed the use of dashes in variable names. Puppet 2.7.20 introduces a configuration option, `allow_variables_with_dashes`, (http://docs.puppetlabs.com/references/2.7.latest/configuration.html#allowvariableswithdashes) which can be set to `true` to restore earlier behavior, although this is strongly discouraged. The option is set to false by default to maintain current behavior. (#10146) `-` in variable names should be deprecated! In commit b26699a2 I fixed an accidentally introduced change to the lexer, allowing `-` to be part of a variable name. That had lasted for a while and was surprisingly popular. It was also hugely ambiguous around `-` as minus, and led to all sorts of failures - unexpected interpolations to nothing - because of that. A much better strategy would have been to deprecate the feature, issue proper warnings, and include an option to allow users to toggle the behaviour. Initially defaulting that to "permit", and eventually toggling over to "deny", would have made the whole experience much smoother - even if this was totally documented as not working, and was a clear bug that it changed. So, thanks to prompting from Benjamin Irizarry, we do just that: introduce the configuration option, default it to "deny" to match current behaviour, but allow users the choice to change this back. Please be aware that allowing variables with `-` might break all sorts of things around, for example, Forge modules though. Most people write code to the documented standard, and their code might well totally fail to work with this changed away from the default! Signed-off-by: Daniel Pittman ## Puppet 2.7.20 Changelog ## Adrien Thebo (1): 367926a (#15264) Custom title patterns can fail cryptically. Andrew Parker (15): 65b35a8 (Maint) Simplify CONTRIBUTING.md 9e26fe0 (#10915) Fix tests to work with new parameter checking d2e5268 (#10915) Add test for provider throwing NoMethodError b48a172 (Maint) Fix syntax and semantic erros in test 5e3fbca (Maint) Remove fragile test dc50ec7 (#16922) Quote strings that contain ":" 13ab956 (#16791) Revert "Merge branch 'perf/2.7.x/backport-activesupport-hook-disabling' of https://github.com/daniel-pittman/puppet into 2.7.x" 1e5baee (#16791) Revert "Maint: Fix intermittently failing spec test" 3cda4f4 (#16791) Revert "Merge branch 'feature/2.7.x/json-terminus-backport' of https://github.com/daniel-pittman/puppet into 2.7.x" aba3c67 (#16791) Re-instate deprecated symbolize and symbolizehash! d892859 (#16791) Remove tests for unused behavior bd0caf5 (#17260) Warn when variables contain hyp
[Puppet Users] Announce: Puppet 2.7.20-rc1 Available
1820927 (Maint) Stop watchr from reading non-existent spec.opts 1a432fd (#15193) Document how to use the static compiler 2bbc4e4 Document the different forms of catalogs to help test writers 58f9679 (#15193) Add spec test coverage for static compiler 94aaf15 (#15193) Fix StaticCompiler#store_content 2b06b7e (#15193) Fix windows failing on unix style paths 315ebad (#2888) Add settings catalog info to README_DEVELOPER 61a34d3 (#2888) Fix race condition with puppetdlockfile e6865c4 (maint) Update mailmap for git shortlog b55d885 (#16798) Update revocation by serial number documentation 92f0688 (#16798) Add more tests to cover revoke by serial number Jeff Weiss (5): 6dcf122 (#15731) Full certificate metadata for pson b61d041 (#15731) explicit fingerprint digest for pson 60a6a2a (#14515) Tests fail with mocha 0.11.4 7b4ac10 (#15731) Move explicit fingerprints to hash f9463ea (#15731) Add clarifying comments to host.rb Josh Cooper (32): ed22b06 (maint) Include backtrace in re-raised exception c95bda7 (maint) Whitespace cleanup f2a4cca (maint) Remove spurious `puts` line bbdbb06 (maint) Consolidate flat file tests d9c7698 (maint) Refactor filetype specs 7a72361 (#14283) Raise an error when crontab returns non-zero on AIX 1d80007 (#14283) Call Tempfile#close and #unlink separately 86dac63 (Maint) Skip crontab filetype tests on Windows e067c2a (#15693) Allow restart command to be specified 4ffc02d (Maint) Enable colorized rspec output on Windows 13e0109 (#15591) Skip test that causes segfault on Windows 1075b74 (#15560) Refactor LogonUser 67b9227 (#15560) Create the user's profile if managehome is true 5e84c97 (#15560) Delete user's profile after deleting account 489352b (#16119) Recognize carriage return escape sequence b67e4dc (#16019) Don't add Unix paths to Windows search path 1a9d122 Maint: Fix leaked tempfile handle a753b86 Maint: Fix inconsistent expect-should usage bd875f5 (#16208): Correct spec test to match new failed parameter message 68c61fa (#16347) Replace \x92 character with apostrophe e84f448 (#16347) Qualify references to windows-pr gem e45961f Maint: Fix intermittently failing spec test da3aea4 (#16581) Refactor code for converting string and binary sids be848e6 (#16581) Use win32-security gem to resolve SIDs 3d360e7 (#16581) Documentation changes 9291ae2 (#16581) Use native Win32 APIs to resolve SIDs in providers c86e685 (#16581) Use native Win32 APIs to resolve SIDs in file provider c60a82d (#16581) Deprecate sid_for_account f08fc39 (#16581) Refactor code for sid validation 5c96254 (#16581) Fix mis-stubbed test 28229d7 Revert "(#17458) Load 'puppet' at the right time" fd92eb1 (#17458) Partial revert of "don't rebuild regexp every time" Ken Barber (1): fcd4957 (#15521) Convert to using host stub wrapper Ken Dreyer (2): e0b1e40 (#7442) solaris: add tests for password_max_age attribute 08c62da (#7442) solaris: return "-1" for password_max_age when password aging is disabled Lee Lowder (1): f08dd53 (#15940) Update puppet doc to ignore files and templates in modules Markus Roberts (1): 368a1cb Fix for #3984 -- SELinux warns about changes it doesn't actually make Matthaus Owens (2): f8a4ddc (#16376) Fix rails compatibility layer for activerecord < 3.0 858e4b4 Update Rakefile to make rspec optional Michael Stahnke (1): 0c1991f Remove the asc file from the source of spec file Moses Mendoza (16): 77afeba Add yaml files db74432 Switch off building gem for 2.7.x 5dc896b Move redhat spec file to erb template in ext/redhat 302248b Add debian packaging artifacts and template a670a4f Move and template all apple pkging artifacts to ext/osx b1648b2 Fixup Rakefile to use packaging repo 2ea1e98 Add in manpage listings that should have been there 67f8b0b Remove broken dual build-requires of facter in redhat spec 82ebe28 Remove version check regex from puppet 0a72c5c Fix yum repo path in yaml file a1c4467 Fixup apple package plist for use with packaging repo b2e31b5 fail better in package repo rake tasks 6da5aa8 Replace dashes with dots for gem version b1adcd2 Fix build targets for 2.7.x fc6571e rm packaging artifacts in rpm spec, debian rules 1d01f2a Update lib/puppet/version.rb for 2.7.20-rc1 Neil Hemingway (1): c305a32 (#11042) indirect via the property to convert group names to numbers Nick Fagerlund (4): adfc27e Maint: Fix borked help/man output for node clean b2c3675 Fix typo in create_resources function's description string 7efbfc6 Maint: Large or complex HEREDOC strings w/ no interpolation
Re: [Puppet Users] Announce: Puppet-Dashboard 1.2.14 Available
On Fri, Nov 9, 2012 at 12:54 PM, Moses Mendoza wrote: > On Fri, Nov 9, 2012 at 5:34 AM, Stefan Heijmans > wrote: >> el5 was not supported, as it has an dependency on ruby 1.8.7 and el5 comes >> default with ruby 1.8.5. >> now that they deliver ruby 1.8.7 with puppet 3 for el5, they perhaps can >> also build them for el5. > > That is indeed true, you're right. So we did:) You should now be able > to `yum install puppet-dashboard` on el5 hosts from the Puppet Labs > yum repo, yum.puppetlabs.com. I also noticed dashboard wasn't quite > happy with the older rubygems in el5, so we built rubygems-1.3.7 for > el5 and added it to the dependencies repo on yum.puppetlabs.com as > well (el5 has rubygems-1.3.1, el6 has 1.3.7). Worked great for me. Just a side note to avoid confusion: rubygems-1.3.1 is in EPEL for el5, not core. > Enjoy. > > Moses -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Announce: Puppet-Dashboard 1.2.14 Available
On Fri, Nov 9, 2012 at 5:34 AM, Stefan Heijmans wrote: > el5 was not supported, as it has an dependency on ruby 1.8.7 and el5 comes > default with ruby 1.8.5. > now that they deliver ruby 1.8.7 with puppet 3 for el5, they perhaps can > also build them for el5. That is indeed true, you're right. So we did:) You should now be able to `yum install puppet-dashboard` on el5 hosts from the Puppet Labs yum repo, yum.puppetlabs.com. I also noticed dashboard wasn't quite happy with the older rubygems in el5, so we built rubygems-1.3.7 for el5 and added it to the dependencies repo on yum.puppetlabs.com as well (el5 has rubygems-1.3.1, el6 has 1.3.7). Worked great for me. Enjoy. Moses -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet-Dashboard 1.2.14 Available
Puppet Dashboard 1.2.14 is a bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.14.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.14: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html === ## Puppet Dashboard 1.2.14 Bug Fixes ## === An error in the packaging of Puppet Dashboard 1.2.13 resulted in several empty directories normally shipped with Puppet Dashboard getting excluded from the source tarball and packages, e.g. 'tmp', 'log', and 'spool'. This release is a re-packaging of Puppet Dashboard 1.2.13 to include these directories. It includes no other changes. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet failing to run
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal wrote:
>
>
>
> On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune wrote:
>>
>> Did you have a version of Puppet on this system previously? This
>> definitely seems like a bug, but it seems like one that only manifests if
>> there's some other copy of Puppet that is also being loaded along with the
>> version you expect.
>>
>
>
> There was a puppet 2.6.8 before and it was failing horribly with all kind of
> ruby file missing.
> So I installed this version using gem. Now I removed gem version puppet to
> get the puppet 2.6.8 back
>
> Now puppet version works again
>
> $ puppet --version
> 2.6.8
>
> But it does not help with this manifest
>
> $ cat ldap.pp
> class { "pam_ldap": }
>
> $ puppet apply ldap.pp
> /usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
> `has_weight' for # (NoMethodError)
> from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `instance_eval'
> from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
> from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
> from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
> from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load_file'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
> from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
> from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in `load_all'
> from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
> from /usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
> `find'
> from /usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
> `find'
> from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
> from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in `main'
> from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
> `run_command'
> from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
> from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
> from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
> from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
> `exit_on_fail'
> from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
> from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
> `execute'
> from /usr/bin/puppet:4
>
>
>
>> -Jeff
>>
>>
>> On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal wrote:
>>>
>>> On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal wrote:
I am getting this error after installing puppet with gem
$ gem install puppet
Fetching: facter-1.6.14.gem (100%)
Fetching: puppet-3.0.1.gem (100%)
Successfully installed facter-1.6.14
Successfully installed puppet-3.0.1
2 gems installed
Installing ri documentation for facter-1.6.14...
Installing ri documentation for puppet-3.0.1...
Installing RDoc documentation for facter-1.6.14...
Installing RDoc documentation for puppet-3.0.1...
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
Could not find main page README.md
$ puppet --version
Error: Could not intialize global default settings: Error converting
value for param 'factpath': Could not find value for $confdir
google search found this link and that is already fixed for this version
https://github.com/puppetlabs/puppet/pull/750
Please advise.
>>>
>>> I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
>>>
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
>>>
>>>
>>>
>>> --
>>> Asif Iqbal
>>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>> A: Because it messes up the order in which people normally read text.
>>> Q: Why is top-posting such a bad thing?
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to puppet-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> puppet-users+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>> --
>> Y
[Puppet Users] Announce: Facter 1.6.14 Available
Facter 1.6.14 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.14.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter or by using `gem install facter`. Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.14.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.14: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Fixes targeted at this version in our bug tracker: http://projects.puppetlabs.com/versions/330 ## Facter 1.6.14 Changelog ## Alex Harvey (3): 278e813 (#14764) Stop calling enum_cpuinfo and enum_lsdev on unsuitable platforms 8063ffe (#13535) Fix uptime; use `uptime` instead of `who -b` 521ae22 (#16506) Fix illegal option error from uname on hpux Andrew Parker (1): 213672f (Maint) Remove aliases for spec from Rakefile Jeff McCune (9): 047a2d9 (#16526) Fix physicalprocessorcount fact on Solaris d136414 (#16527) Fix processorcount fact on Solaris 1077baa (maint) Add newlines to all files (whitespace only) 5b3d509 (maint) Remove rspec from shebang lines 462756a (maint) Add mailmap for git shortlog cdbd05c (maint) Cleanup of the virtual spec tests. 2ed2575 (maint) Properly indent virtual_spec.rb cf43fc0 (#8210) Add a heavy virtual fact using virt-what 62478ff (#11609) Fix processorX facts for AIX systems Josh Cooper (2): 1f94855 (#16829) Change how bundler is detected b81528d Maint: fix mismatched stub Matthaus Owens (1): 75bd002 (#16397) Update selinux_mount_point for 1.8.5 compatibility Moses Mendoza (1): 4ccf1be return vendor field and retab Patrick Carlisle (1): 0b56c1a Only load rubygems in bin/facter -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Facter 1.6.14-rc1 Available
Facter 1.6.14-rc1 is a maintenance release candidate in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.14-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter or by using the --pre option to gem install. Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.14-rc1.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.14-rc1: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Fixes targeted at this version in our bug tracker: http://projects.puppetlabs.com/versions/330 ## Facter 1.6.14-rc1 Changelog ## Alex Harvey (3): 278e813 (#14764) Stop calling enum_cpuinfo and enum_lsdev on unsuitable platforms 8063ffe (#13535) Fix uptime; use `uptime` instead of `who -b` 521ae22 (#16506) Fix illegal option error from uname on hpux Andrew Parker (1): 213672f (Maint) Remove aliases for spec from Rakefile Jeff McCune (9): 047a2d9 (#16526) Fix physicalprocessorcount fact on Solaris d136414 (#16527) Fix processorcount fact on Solaris 1077baa (maint) Add newlines to all files (whitespace only) 5b3d509 (maint) Remove rspec from shebang lines 462756a (maint) Add mailmap for git shortlog cdbd05c (maint) Cleanup of the virtual spec tests. 2ed2575 (maint) Properly indent virtual_spec.rb cf43fc0 (#8210) Add a heavy virtual fact using virt-what 62478ff (#11609) Fix processorX facts for AIX systems Josh Cooper (2): 1f94855 (#16829) Change how bundler is detected b81528d Maint: fix mismatched stub Matthaus Owens (1): 75bd002 (#16397) Update selinux_mount_point for 1.8.5 compatibility Moses Mendoza (1): 4ccf1be return vendor field and retab Patrick Carlisle (1): 0b56c1a Only load rubygems in bin/facter -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet Dashboard 1.2.13-rc1 Available
Puppet Dashboard 1.2.13-rc1 is a maintenance and bugfix release candidate of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13-rc1.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.13-rc1: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html == ## Puppet Dashboard 1.2.13-rc1 Bug Fixes ## == (#17161) Fix stylesheet URLs for IE colorbox images The colorbox CSS looks for the IE images in /images/internet_explorer. The correct location is /stylesheets/images/internet_explorer. Update debian and redhat init script to use INT instead of term to stop Previously the debian init script didn't pass --signal to the start-stop-daemon, which defaults to TERM. Dashboard runs out of webrick by default, which catches and ignores TERM, but will respond to INT and stop sanely. Currently, running 'service puppet-dashboard stop' returns [2012-03-27 10:24:17] ERROR SignalException: SIGTERM /usr/lib/ruby/1.8/webrick/server.rb:91:in `select' and then waits for the retry timeout, at which point start-stop-daemon SIGKILLs the ruby process. If --signal is set to INT in the init script, running 'service puppet-dashboard stop' returns [2012-03-27 10:28:35] INFO going to shutdown ... [2012-03-27 10:28:35] INFO WEBrick::HTTPServer#start done. Exiting which is the expected behavior. The redhat init script suffered from a similar problem, adding -INT to the killproc call speeds up the `service puppet-dashboard stop` call as killproc doesn't need to wait and see if the process has ended, as INT is responded to immediately by webrick. (#9296) Fix loading rack for rubygems >= 1.8 Rubygems version 1.8 broke some of the ways vendored gems used to work in Rails 2. This commit updates the config/environment.rb to add all of the gem libs to the rails autoload_paths. It also updates the actionpack action_controller library to not call out to gem explicitly. We know that the correct rack version is being supplied in the vendored gems, so the following require 'rack' line will succeed. This also munges the load path in config/boot.rb because boot.rb doesn't load environment.rb right away, and so can't find rack, due to the same gem problem. So this uses the same loop as in environment.rb, but instead of the rails autoload_paths, it adds the libs to $:, or $LOAD_PATH. == ## Puppet Dashboard 1.2.13-rc1 Changelog ## == Branan Purvine-Riley (1): c2e4a4a (#17161) Fix stylesheet URLs for IE colorbox images Matthaus Owens (2): a3f2588 (#9296) Fix loading rack for rubygems >= 1.8 5378b46 Update debian and redhat init script to use INT instead of term to stop Moses Mendoza (1): ee6d3c3 Update VERSION, CHANGELOG for 1.2.13-rc1 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Hiera 1.1.1-rc1 Available
Hiera 1.1.1-rc1 is a release candidate in the 1.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/hiera/hiera-1.1.1-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/hiera or by using the --pre option to gem install. Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/hiera-1.1.1-rc1.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.1.1-rc1: http://projects.puppetlabs.com/projects/hiera/ === ## Hiera 1.1.1-rc1 Bug Fixes ## === (#16831) Change how bundler is detected The constant `::Bundler::Setup` isn't defined in the latest version, instead using just `::Bundler` to detect whether it's been loaded. See also #16757 Only load rubygems in bin/hiera We should not require rubygems when used as a library. When invoked from the command line we require rubygems if bundler has not been loaded. If bundler has been loaded we assume rubygems is already loaded if it needs to be, as requiring rubygems after loading bundler can break the bundler setup. === ## Hiera 1.1.0-rc1 Changelog ## === Josh Cooper (1): 423b37c (#16831) Change how bundler is detected Moses Mendoza (1): 7c3b6f3 Update lib/hiera.rb for 1.1.1-rc1 Patrick Carlisle (1): 6a94ef9 Only load rubygems in bin/hiera -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 3.0.1 Available
Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick Carlisle, Stijn Tintel, and Will Farrington. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.0.1.tar.gz RPMs are available at https://yum.puppetlabs.com Debs are available at https://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.0.1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.0.1.msi See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.1: https://projects.puppetlabs.com/projects/puppet/ Puppet 3.0.1 Changelog Andrew Parker (9): (#15717) Require puppet/run in the agent (#15717) Allow pluginsync as an option to Puppet::Run (#16698) Do not set Node cache_terminus for storedconfigs (#16698) Add acceptance test for using store configs with an enc (#16922) Quote strings that contain ":" (#16922) Quote strings that contain ":" (#16698) Exclude enc+storeconfig test from solaris (Maint) Fix acceptance test to work on centos5 (Maint) Exclude test from windows Jeff McCune (6): (maint) Add .yardopts file (maint) Add yard generated documentation to git ignore (#16637) Add spec test for non-root puppet master confdir and vardir (#16637) Fix default confdir and vardir with puppet master as normal user (Maint) Update config.ru to fix issue with vardir (#16769) Fix header too long error with ExportCertData Josh Cooper (9): (#15717) Acceptance tests for puppet kick (#15717) Kick agent using its fqdn (#16757) Move rubygems require to application entry point (#16757) Deprecate Puppet.features.rubygems? (#16757) Don't require rubygems (#16757) Prevent using rubygems when bundler is in use (#16801) Remove mongrel references from manpage (#16801) Remove mongrel references (#17000) Use --no-client argument to prevent agent from starting Matthaus Litteken (1): (#16376) Fix rails compatibility layer for activerecord < 3.0 Matthaus Owens (9): (#16801) Remove mongrel references from init scripts Maint: Retab puppetmaster init scripts Maint: Remove unused $prog variable from redhat puppetmaster init script Update redhat logrotate to signal correct process Remove unused suse packaging files (#16801) Update suse server.init and remove mongrel refs Update suse client.init for new pidfile, process name Update suse puppet.spec for Telly Update PUPPETVERSION for 3.0.1-rc1 Moses Mendoza (2): fail better in package repo rake tasks Update PUPPETVERSION for 3.0.1 Nick Fagerlund (1): (#16585) Remove dead ldapnodes setting Niels Abspoel (2): This will fix Refactor #16643. sample_module.pp refactored text: include sample-module into include sample_module Patrick Carlisle (2): (#16757) Only load rubygems in bin/puppet (#16757) Don't load rubygems if bundler is running Stijn Tintel (2): (#16801) Remove lib/puppet/network/http/mongrel (#16801) Remove mongrel_spec.rb as it is no longer in use. Will Farrington (1): Fix up dependencies for Hiera and Facter in RubyGems. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: PuppetDB 1.0.1 Available
PuppetDB 1.0.1 is now available for download! This is a bug-fix release of PuppetDB. # Downloads == Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ Available for use with Puppet Enterprise 2.5.1 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # 1.0.1 Changelog == Many thanks to the following people who contributed patches to this release: Deepak Giridharagopal Nick Lewis Matthaus Litteken Chris Price Fixes: (#16180) Properly handle edges between exported resources This was previously failing when an edge referred to an exported resource which was also collected, because it was incorrectly assuming collected resources would always be marked as NOT exported. However, in the case of a node collecting a resource which it also exports, the resource is still marked exported. In that case, it can be distinguished from a purely exported resource by whether it's virtual. Purely virtual, non-exported resources never appear in the catalog. Virtual, exported resources are not collected, whereas non-virtual, exported resources are. The former will eventually be removed from the catalog before being sent to the agent, and thus aren't eligible for participation in a relationship. We now check whether the resource is virtual rather than exported, for correct behavior. (#16535) Properly find edges that point at an exec by an alias During namevar aliasing, we end up changing the :alias parameter to 'alias' and using that for the duration (to distinguish "our" aliases form the "original" aliases). However, in the case of exec, we were bailing out early because execs aren't isomorphic, and not adding 'alias'. Now we will always change :alias to 'alias', and just won't add the namevar alias for execs. (#16407) Handle trailing slashes when creating edges for file resources We were failing to create relationships (edges) to File resources if the relationship was specified with a different number of trailing slashes in the title than the title of the original resource. (#16652) Replace dir with specific files for terminus package Previously, the files section claimed ownership of Puppet's libdir, which confuses rpm when both packages are installed. This commit breaks out all of the files and only owns one directory, which clearly belongs to puppetdb. This will allow rpm to correctly identify files which belong to puppet vs puppetdb-terminus. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet Dashboard 1.2.12 Available
Puppet Dashboard 1.2.12 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.12.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.12: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html = ## Puppet Dashboard 1.2.12 Highlights ## = (#16428) more accurate CONTRIBUTING.md This just updates the docs to indicate what I needed to do to get tests running. Modulo any actual inaccuracies, I think having something here is better than nothing. If there are simplifications or other fixes to make on top of this, those can come later. Specify the location of the favicon in error pages Prior to this commit, rendering an error page would itself result in an error if the default favicon.ico file is protected by an authentication system that has a whitelist of allowed routes. == ## Puppet Dashboard 1.2.12 Changelog ## == Dustin J. Mitchell (1): 6c0c8e0 (#16428) more accurate CONTRIBUTING.md Joshua Harlan Lifton (1): 9fea666 Specify the location of the favicon in error pages Matthaus Litteken (2): 5ac77d0 Update default cows and mocks 8759c5c Updating CHANGELOG for Puppet Dashboard 1.2.12-rc1 Moses Mendoza (1): 83e926b fail better in package repo rake tasks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Hiera 1.1.0 Available
Hiera 1.1.0 is a release in the 1.x branch with bug fixes and features. Downloads are available at: * Source: https://downloads.puppetlabs.com/hiera/hiera-1.1.0.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/hiera Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/hiera-1.1.0.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.1.0: http://projects.puppetlabs.com/projects/hiera/ === ## Hiera 1.1.0 Highlights ## === (#16427) Fix inaccurate usage hint in help Usage in help was provided as "Usage: hiera [options]", which is inaccurate. This commit uses opts.banner in the option parser to override that, as well as provide some context about the arguments. Add json backend to hiera. This commit brings the json backend and corresponding spec test from hiera-json into hiera. The spec test has been updated to move some of its requires into the spec_helper in a previous commit. This commit also updates the project_data.yaml to add a json dependency to hiera to the gem, deb and rpm packages. Edit example hiera.yaml to fix bogus variable and include default datadir A Puppet scope has no $certname variable, and we don't do anything to add one. Instead, Puppet has the following two variables: - $settings::certname - the puppet master's certname - $clientcert - the agent node's certname Of the two, we want $clientcert. This commit also calls out the location of the default datadir. Clarify help for some options This commit clarifies the function of the -a and -h flags, and improves the wording of the MCollective and inventory options. === ## Hiera 1.1.0 Changelog ## === Andrew Parker (1): f0f89ca (Maint) Lenient checks for looked up data Daniel Pittman (1): 580d39e Fix expect/should for RSpec 3 compatibility Matthaus Litteken (8): 66fc90e Refactor specs, remove spec.opts d36e0f5 Add json backend to hiera. f3f4653 (maint) Fixup hiera.spec for el5 oddities, rpmlint issues a9aa024 (maint) Fixup json dependency for redhat 114944d (maint) Config=>RbConfig in hiera.spec.erb 5253f39 (maint) Remove CHANGELOG from Hiera fe5f8b9 Update default cows and mock targets db60ecc Update VERSION for Hiera 1.1.0-rc1 Mitchell Hashimoto (1): c895013 Additional logging when finding keys in the YAML backend Moses Mendoza (3): f7334ba Fixup apple package plist for use with packaging repo 3a37348 fail better in package repo rake tasks d1c175b Update debian packaging for ruby 1.9 Will Hopper (1): ff2bbc6 Update Debian packaging rake task to correctly create the orig.tar.gz nfagerlund (3): b4e6e2f Edit example hiera.yaml to fix bogus variable and include default datadir c56ff30 (#16427) Fix inaccurate usage hint in help 562a7cc Clarify help for some options rahul (1): 8e7c748 (packaging) provider IPS packaging tasks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Facter 1.6.13 Available
Facter 1.6.13 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.13.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.13.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.6.13: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki ## Facter 1.6.13 Release Notes ## (#1415) Added case for Linux/IB to get correct IB address or fail predictably. Originally, facter displayed a truncated infiniband MAC address. Now, If the interface starts with ib, use one of two methods to get the infiniband MAC address or fails with a MAC address of all FF otherwise. (#16005) Puppet agent generates ifconfig warnings on InfiniBand systems fix Whenever ifconfig was called on systems with Ib interfaces, it would echo direcly to STDERR. This commit suppresses ifconfig STDERR messages. Improve rubysitedir fact With ruby-1.9.3 -- at least on Fedora 17 -- trawling through the library paths looking for the directory does not work. Using RbConfig seems more reliable and much simpler. (#5205) Update facter manpage This commit doesn't handle the request in the ticket of dynamically generated manpage, but it does update the man page to have updated flags and help, correct license, copyright holder and copyright year. It also fills in the name of the program for the manpage so that the header doesn't look quite so mysterious. = ## Facter 1.6.13 Changelog ## = Daniel Pittman (1): b5fe6d0 Update copyright years in LICENSE Garrett Honeycutt (4): 5f64f45 removes trailing whitespace 561c156 fixes formatting bug in man page 53b7ecc removes generator comments ce581f8 fixes spacing on puppet option to be in line Matthaus Litteken (13): 41fc7e0 (#5205) Update facter manpage eb87175 (maint) Replace deprecated Config with RbConfig in debian/rules 8697472 Remove sbin references from install.rb efe976b Remove RbConfig=>Config monkey_patch 008a8d7 Add --ruby flag to install.rb 29af0cd Remove svn specific code from install.rb d008d35 (maint) Update debian/rules to use new --ruby flag 43d3e68 Update default cows 4cb1030 Remove asc file a source for RPM builds 903b298 Spec file cleanup 25cb69f Remove INSTALL from Facter cc2015d Remove CHANGELOG from Facter e81b3ab Updating FACTERVERSION for facter 1.6.13-rc1 Matthaus Owens (1): 8083990 Update facter debian packaging for 1.9 support Michael Renz (10): 262ef6a (#1415) Added case for Linux/IB to get correct IB address or fail predictably. 240dfac (#1415) ifconfig should not run twice for Linux. d4d0b80 (#1415) Handles ruby hanging of File.read of /sys/class/ with cat. 1c43b91 (#16005) Puppet agent generates ifconfig warnings on InfiniBand systems fix 6c8f5f5 (#1415) ip_spec.rb test added for linux_ifconfig_ib0 1d82907 (#1415) added two methods and spec tests f0858de (#1415) ifconfig_interface should output its output d413e93 (#1415) fixed the regex map a81469e (#1415) ifconfig_interface change. 593c1e2 (#16005) updated ipaddress6_spec.rb and macaddress_spec.rb to reflect updated ifconfig STDERR redirect Moses Mendoza (3): 1b4226c Fixup apple package plist for use with packaging repo 0b85564 (#16341) return epoch to 1.6.x branch 0f15e41 fail better in package repo rake tasks Todd Zullinger (1): caed72f Improve rubysitedir fact rahul (3): b713596 (maint) add packaging artifacts bffa03a (packaging) add ips support 7b51f4a (packaging) ips: add shipping and signing support -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Solaris Packages for Puppet 3.0.0-rc7, Facter 1.6.0 and Hiera 1.0.0
-- Forwarded message -- From: Rahul Gopinath Date: Fri, Sep 21, 2012 at 4:43 PM Subject: [Puppet-dev] Solaris Packages for Puppet 3.0.0, Facter 1.6.0 and Hiera 1.0.0 To: puppet-users@googlegroups.com, puppet-...@googlegroups.com Hello, For the first time, experimental Solaris 11 IPS packages for Puppet 3.0.0-rc7, Facter 1.6.12 and Hiera 1.0.0 are available under http://downloads.puppetlabs.com/solaris They are: puppet@3.0.0,5.11-9211.p5p facter@1.6.12,5.11-819.p5p hiera@1.0.0,5.11-116.p5p The versioning scheme for Solaris is different from the default scheme. The versioning scheme is @,- . Specifically the RC candidates and the Final version are distinguished only by their build number which is monotonic. To install these packages, download them from the above link and use IPS pkg command. E.g for puppet pkg install -g ./puppet@3.0.0,5.11-9211.p5p puppet Note that since this is experimental and each product is in its own repository archive, Hiera and Factor need to be installed first before Puppet is installed. To Solaris users, we would greatly appreciate your feedback on these packages. We are also in the process of setting up public IPS repositories and will update you as we make progress. Rahul -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-...@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: PuppetDB 1.0 Available
PuppetDB 1.0 is now available! PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts. Much more information is available on the Puppet Labs blog: http://puppetlabs.com/blog/introducing-puppetdb-put-your-data-to-work/ ...and on the docs site: http://docs.puppetlabs.com/puppetdb/1/ ...and there will also be 2 talks involving PuppetDB at next week's PuppetConf. What can it do for you? * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It's already in production at many sites, handling thousands of nodes and millions of resources * It hooks into your Puppet infrastructure using Puppet’s pre-existing extension points (catalog/facts/resource/node terminuses) * It’s much faster, much more space-efficient, and much more scalable than current storeconfigs and the current inventory service. * We can handle a few thousand nodes, with several hundred resources each, with a 30m runinterval on our laptops during development. * It stores the entire catalog, including all dependency and containment information * It exposes well-defined, HTTP-based methods for accessing stored information * Documented at http://docs.puppetlabs.com/puppetdb * It presents a superset of the storeconfigs and inventory service APIs for use in scripts or by other tools * In particular, we support arbitrarily nested boolean operators * It decouples catalog and fact storage from the compilation process * PuppetDB obsoletes previous puppetq functionality * It works Very Hard to store everything you send it; we auto-retry all storage requests, persist storage requests across restarts, and preserve full traces of all failed requests for post-mortem analysis * It’s secured using Puppet’s built-in SSL infrastructure * It’s heavily instrumented and easy to integrate its performance info into your monitoring frameworks We encourage you to try it out, hammer it with data, and let us know if you run into any issues! # Downloads Available in native package format at http://yum.puppetlabs.com http://apt.puppetlabs.com Source (same license as Puppet): http://github.com/puppetlabs/puppetdb Available for use with Puppet Enterprise 2.5.1 and later at http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ Puppet module (Puppet Enterprise support is forthcoming): http://forge.puppetlabs.com/puppetlabs/puppetdb # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard 1.2.11 rpm is missing the build_defaults.yaml file
Hi Jo, Good catch. While working with packaging, we modified the puppet-dashboard top-level rakefile to try loading a couple yaml files in ext, and a rescue prints the message you see if they're not there. Alas, those yaml files don't make it into the rpm, which is why you're seeing the message. It doesn't affect dashboard's other rake tasks, e.g. db:migrate in any way, but that error message is certainly an unsavory user experience. The next release of puppet dashboard will address this. Thanks for reporting this. Moses On Tue, Sep 18, 2012 at 9:56 AM, Jo Rhett wrote: > I installed the RPM available from yum.puppetlabs.com on CentOS 6.x and I > receive the following error when upgrading from 1.2.10 to 1.2.11. > > $ rake db:migrate RAILS_ENV=production > certificate_path: 'certs/puppet.cert.pem' > private_key_path: 'certs/puppet.private_key.pem' > public_key_path: 'certs/puppet.public_key.pem' > > (in /usr/share/puppet-dashboard) > Unable to read the packaging repo info from ext/build_defaults.yaml > $ ls ext > passenger puppet > $ find ext > ext > ext/passenger > ext/passenger/dashboard-vhost.conf > ext/puppet > ext/puppet/puppet_dashboard.rb > > Dashboard appears to be working fine, but the error provides some cause for > concern. > > On Sep 13, 2012, at 3:14 PM, Matthaus Owens wrote: > > Puppet Dashboard 1.2.11 is a maintenance and bugfix release of Puppet > Dashboard. > > This release is available for download at: > https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.11.tar.gz > > Debian packages are available at > https://apt.puppetlabs.com > > RPM packages are available at > https://yum.puppetlabs.com > > See the Verifying Puppet Download section at: > http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet > > Please report feedback via the Puppet Labs Redmine site, using an > affected version of 1.2.11: > http://projects.puppetlabs.com/projects/dashboard > > Documentation is available at: > http://docs.puppetlabs.com/dashboard/index.html > > Puppet Dashboard 1.2.11 Highlights > > (#15196) Make items per page configurable >This commit adds the ability to specify the number of specific items >per page displayed by dashboard in the settings.yml file, including >nodes, classes, groups and reports per page. > > Autorefresh link gen fixed to work under passenger >Autorefresh link generation did not take root_path for the >application into consideration. Using File.join() to try and avoid >multiple /'s getting into generated url which would cause routing >problems. > > Shift to using packaging repo for packaging tasks >This release introduces Dashboard's use of the packaging repo at >https://github.com/puppetlabs/packaging for packaging automation. From >source, doing a rake package:bootstrap clones packaging tasks into >ext/packaging and adds rake tasks for packaging of tar, srpm, rpm, and >deb using tools such as rpmbuild and debuild, as well as >puppetlabs-namespaced tasks that use chroot environment tools and are >keyed to specifically interacting with the puppetlabs environment. The >packaging repo works in tandem with the new package-builder modules >designed to set up hosts for packaging, >https://github.com/puppetlabs/puppetlabs-rpmbuilder, and >https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much >a work in progress, but a model for how packaging automation could >improve across many Puppet Labs projects. > > Puppet Dashboard 1.2.11 Changelog > > Boyan Tabakov (2): > d6619a1 Updated debian postinst script to link properly the > settings.yml file to puppet-dashboard config directory. > a8a97dc Fixed linking of database.yml in debian postinst to use > absolute path. > > Erik Dalén (1): > ffe7bdd (#15196) Make items per page configurable > > Jani Mikkonen (1): > df5a20a Autorefresh link gen fixed to work under passenger > > Joshua Harlan Lifton (2): > c64c013 (#10477) Clean up log files by moving message to debug > a8e2586 Fix spec tests broken by commit c64c013 > > Matthaus Litteken (2): > 8806f60 (#15291) Add Vendor tag to Puppet-Dashboard spec file > c0592af Update CHANGELOG, VERSION for 1.2.11 > > Moses Mendoza (10): > 3abf9df Move packaging up to ext to avoid conflict with pkging repo > 71d302a re-template debian changelog > 4201990 Fixup redhat spec erb for packaging repo > 42030b8 Remove obsolete package.rake file > da22ddd Add packaging data files > 8f03e6c Add VERSIO
[Puppet Users] Announce: Puppet 3.0.0-rc6 Available
b8ca748 (#11727) Support STDIN for `puppet parser validate`
f10d364 maint: remove .rspec entirely
bd9c3b6 Revert "(#15852) Remove version check from puppet_spec.rb"
294fae2 Port the SemVer test from Test::Unit to RSpec.
86fa102 Fix a test broken by the improved parameter error reporting.
d260b90 RSpec 3 is deprecating `expect {}.should` - respect that.
c47b2a6 RSpec 3 is deprecating `expect {}.should` - respect that.
Dustin J. Mitchell (3):
cb3c912 (#16208) Better error messages for failed parameter validation
f30af22 (#16208) use #{ref} instead of #{type} #{title} as
suggested by dpittman
d9ab06f (#16208) fix tests
Eric Sorenson (3):
700caba (#15739) Bump report_version since #10064 change its format
775d0dc Revert "(#15797) Change the argument to chkconfig from
'on' to 'reset'"
0620497 (#15797) Update chkconfig test to reflect reality
Erik Dalén (1):
b53f251 (#16175) Touch filebuckets contents when we get a new path
Gleb Arshinov (1):
c8152d4 (#15920) Make forward-sexp ignore comments in puppet-mode.el
Jeff McCune (7):
576fd56 Whitespace only cleanup
1820927 (Maint) Stop watchr from reading non-existent spec.opts
1a432fd (#15193) Document how to use the static compiler
2bbc4e4 Document the different forms of catalogs to help test writers
58f9679 (#15193) Add spec test coverage for static compiler
94aaf15 (#15193) Fix StaticCompiler#store_content
2b06b7e (#15193) Fix windows failing on unix style paths
Jeff Weiss (4):
6dcf122 (#15731) Full certificate metadata for pson
b61d041 (#15731) explicit fingerprint digest for pson
7b4ac10 (#15731) Move explicit fingerprints to hash
f9463ea (#15731) Add clarifying comments to host.rb
Josh Cooper (10):
4ffc02d (Maint) Enable colorized rspec output on Windows
13e0109 (#15591) Skip test that causes segfault on Windows
1075b74 (#15560) Refactor LogonUser
67b9227 (#15560) Create the user's profile if managehome is true
5e84c97 (#15560) Delete user's profile after deleting account
489352b (#16119) Recognize carriage return escape sequence
b67e4dc (#16019) Don't add Unix paths to Windows search path
1a9d122 Maint: Fix leaked tempfile handle
a753b86 Maint: Fix inconsistent expect-should usage
bd875f5 (#16208): Correct spec test to match new failed parameter message
Markus Roberts (1):
368a1cb Fix for #3984 -- SELinux warns about changes it doesn't
actually make
Moses Mendoza (18):
77afeba Add yaml files
db74432 Switch off building gem for 2.7.x
5dc896b Move redhat spec file to erb template in ext/redhat
302248b Add debian packaging artifacts and template
a670a4f Move and template all apple pkging artifacts to ext/osx
b1648b2 Fixup Rakefile to use packaging repo
2ea1e98 Add in manpage listings that should have been there
67f8b0b Remove broken dual build-requires of facter in redhat spec
82ebe28 Remove version check regex from puppet
0a72c5c Fix yum repo path in yaml file
7ada9e4 Fixup debian artifacts for 3.x
09cbc1a Fixup for different source paths
5688f56 remove old tasks and pull out of rake subdir
f2e8ee0 Move all packaging artifacts from conf to ext
bd367e1 Remove debian manpages that are obsolete in 3.x
f1c9661 Remove old apple package rake task
c421b23 Update lib/puppet/version.rb for 3.0.0-rc6
08a4f76 remove non-applicable artifacts in packaging
Nick Fagerlund (2):
adfc27e Maint: Fix borked help/man output for node clean
7efbfc6 Maint: Large or complex HEREDOC strings w/ no
interpolation should be single-quote type
Patrick Carlisle (16):
fe330c9 (#16058) Add setting to configure catalog cache
fae8591 (#16058) Set pson as default catalog cache format
4005db3 Add a terminus setting type
b7ddf3e (#16058) Add setting to configure catalog cache
8c32120 (#16058) Set pson as default catalog cache format
44395aa Add a terminus setting type
6f556ef Don't pollute Functions namespace in shellquote function
ca36893 Backport fix for commandline spec
14d1fdc Don't make executables in /tmp in posix_spec
a3edf1a (#15733) Remove mongrel support
54c6a9b (#15733) Remove servertype setting
263acc3 (#15733) Simplify bindaddress logic for webrick
15c716e (#13563) Verify CSRs against the embedded public key
0162269 (#15733) Use real arguments for Puppet::Network::Server
05c10f7 (#15733) Remove excess hash arguments for webrick
f0ff559 (#16275) Don't set $environment as a local fact
S. Zachariah Sprackett (1):
04ba8e2 Add stdin parsing to puppet parser validate
Stefan Schulte (7):
e111f56 maint: Rearrange tests in useradd unittests
03c7ddf1 maint: Reduce stubbing in us
[Puppet Users] Announce: Puppet Dashboard 1.2.11-rc1 Available
Puppet Dashboard 1.2.11-rc1 is a maintenance and bugfix release candidate of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.11-rc1.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.11-rc1: http://projects.puppetlabs.com/projects/dashboard Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html 1.2.11-rc1 Highlights === ffe7bdd (#15196) Make items per page configurable This commit adds the ability to specify the number of specific items per page displayed by dashboard in the settings.yml file, including nodes, classes, groups and reports per page. Autorefresh link gen fixed to work under passenger Autorefresh link generation did not take root_path for the application into consideration. Using File.join() to try and avoid multiple /'s getting into generated url which would cause routing problems. Shift to using packaging repo for packaging tasks This release introduces Dashboard's use of the packaging repo at https://github.com/puppetlabs/packaging for packaging automation. From source, doing a rake package:bootstrap clones packaging tasks into ext/packaging and adds rake tasks for packaging of tar, srpm, rpm, and deb using tools such as rpmbuild and debuild, as well as puppetlabs-namespaced tasks that use chroot environment tools and are keyed to specifically interacting with the puppetlabs environment. The packaging repo works in tandem with the new package-builder modules designed to set up hosts for packaging, https://github.com/puppetlabs/puppetlabs-rpmbuilder, and https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much a work in progress, but a model for how packaging automation could improve across many Puppet Labs projects. 1.2.11-rc1 Changelog === 101af75 Update supported debian versions and cows e6f6acf Fixup Rakefile for setting up packaging repo 8f03e6c Add VERSION file to source da22ddd Add packaging data files 42030b8 Remove obsolete package.rake file 4201990 Fixup redhat spec erb for packaging repo 71d302a re-template debian changelog 3abf9df Move packaging up to ext to avoid conflict with pkging repo a8e2586 Fix spec tests broken by commit c64c013 ffe7bdd (#15196) Make items per page configurable c64c013 (#10477) Clean up log files by moving message to debug df5a20a Autorefresh link gen fixed to work under passenger 8806f60 (#15291) Add Vendor tag to Puppet-Dashboard spec file 5eccef2 (#15523) Update Debian packaging rake task to create the debian and original tarballs 63a0634 Add release number variable to packaging rake task a8a97dc Fixed linking of database.yml in debian postinst to use absolute path. d6619a1 Updated debian postinst script to link properly the settings.yml file to puppet-dashboard config directory. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Facter 1.6.12-rc1 available
Facter 1.6.12-rc1 is a maintenance release candidate in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.12-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter or by using the --pre option to gem install. Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.6.12-rc1.dmg See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using a affected version of 1.6.12-rc1: http://projects.puppetlabs.com/projects/facter/ Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Facter 1.6.12-rc1 Highlights == (#15464) Make contributing easy via bundle Gemfile Without this patch the process of figuring out how to quickly set up a development and testing environment for the Puppet _application_ (not a gem library) is unnecessarily complicated. This patch addresses the problem by providing a Bundler compatible Gemfile that specifies all of the Gem dependencies for the Puppet 2.7 application. Puppet contributors can now easily get a working development and testing environment using this sequence of commands: $ git clone --branch 2.7.x git://github.com/puppetlabs/puppet.git $ cd puppet/ $ bundle install # Install all required dependencies $ rspec The .noexec.yaml file excludes the `rake` command so that the Gemfile doesn't raise an exception if the `rubygems-bundler` Gem is installed and automatically running `bundle exec` for us. The Gemfile.lock contains the exact dependency versions. This file is included in the version control system because we're treating Puppet as an application rather than a library. Shift to using packaging repo for packaging tasks This release introduces Facter's use of the packaging repo at https://github.com/puppetlabs/packaging for packaging automation. From source, doing a rake package:bootstrap clones packaging tasks into ext/packaging and adds rake tasks for packaging of tar, gem, srpm, rpm, and deb using tools such as rpmbuild and debuild, as well as puppetlabs-namespaced tasks that use chroot environment tools and are keyed to specifically interacting with the puppetlabs environment. The packaging repo works in tandem with the new package-builder modules designed to set up hosts for packaging, https://github.com/puppetlabs/puppetlabs-rpmbuilder, and https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much a work in progress, but a model for how packaging automation could improve across many Puppet Labs projects. (#11640) Added support for new OpenStack MAC addresses OpenStack changed the MAC address prefix they use to address an issues with libvirt OpenStack bug: https://bugs.launchpad.net/nova/+bug/921838 Facter 1.6.12-rc1 Changelog === Jeff McCune (2) c0cbe62 (#15464) Make Facter.version settable via Facter.version= 0b49eae (#15464) Make contributing easy via bundle Gemfile Moses Mendoza (18) 3ad05f1 Remove version test from facter fce4b01 fix redhat spec release template variable 903b1d9 Stop using sed to generate the preflight erb 601a967 Use git read-only packaging repo for public access dd3401e Fixup apple packaging e0454df Remove libexec from file list as its only in 2.x 1e7f5b3 Update debhelper compat to 7, add format 6659e61 Fixup redhat spec erb template for f17 6752530 Shift to using packaging repo fe311c2 Remove obsolete tasks directory 900895f Group requires together 8c18e33 Move facter redhat spec file to erb 84f8e10 Add debian build artifacts to facter project d2d3baf Replace rake/gempackagetask with rubygems/gempackagetask 6f58b4e Move tasks out of 'rake' subdirectory db9d154 Move packaging files to ext, rm conf 17243bb Update facter redhat spec for fedora 17 7ca9122 Update a facter build-requires for f17 Matthaus Owens (2) bf6ee4f Retabbed conf/redhat/facter.spec to lineup tag contents. defbfb8 (#15291) Add Vendor tag to Facter spec file Andrew Abrahamowicz (1) d5d2328 (#11640) Added support for new OpenStack MAC addresses -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet-3.0.0-rc5 Available
Puppet 3.0.0-rc5 is a feature release candidate for the 3.x series of Puppet. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc5.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.0.rc5.gem or by using `gem install --pre puppet` Mac packages are available at http://downloads.puppetlabs.com/mac/puppet-3.0.0-rc5.dmg Windows packages are available at http://downloads.puppetlabs.com/windows/puppet-3.0.0-rc5.msi See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.0-rc5: http://projects.puppetlabs.com/projects/puppet/ Puppet 3.0.0-rc5 (Telly) Release Notes = Numbers in parentheses like `(#7788)` indicate a Redmine ticket at http://projects.puppetlabs.com/issues/7788 Notation like `(puppet/pull/998)` indicate a github pull request at https://github.com/puppetlabs/puppet/pull/998 # Summary of Changes This is not an exhaustive summary, but rather an editorialized list of the biggest changes. See the Git changelog for the full monty. ## Cool New Stuff * Performance Improvements - substantial improvements to performance, particularly around catalog compilation. Agent supports JSON serialization for catalog cache, which can be dramatically faster for large catalogs (#16058, #2892) * Data Bindings - hiera will be automatically consulted for values of parameterized classes so you don't need the parser functions. (#11608) * Improved OS/Platform Support - Full Ruby 1.9 support; vastly improved Windows package support; yumrepo now supports ssl options (#3324); better upstart support; better Solaris zone, package and service support; * Loading Plugins from Rubygems - you can now install and use puppet extension code (faces, types, providers) via rubygems. (#7788) * Server Auto-Discovery - Puppet agents can use SRV records in DNS to find CA, master, report, and file servers (#3669) # DSL/Config Changes * Variable Scoping - Dynamic scoping has been removed. http://docs.puppetlabs.com/guides/scope_and_puppet.html * Auth.conf differentiates between names and IPs - There's a new `allow_ip` keyword in auth.conf if you want to permit IP addresses. (PR991) * `unless` is available as a synonym for `if !` (#7762) * Pluginsync now defaults to true - Yep, it's true. (#5521) * Updated `config.ru` syntax -- When running the master under Rack, make sure you update your config.ru to follow the example from ext/rack/files/config.ru in the source distribution. (#15337) # Changed Code Behaviour * External Node Classifier and Environments - If there's a conflict between the environment requested by a client and what's set in the external node classifier, the ENC wins. (#3910) * When running puppet as root, the system-wide `confdir` and `vardir` settings will be used. When running as a non-root user, `confdir` will be `~/.puppet/` and `vardir` will be `~/.puppet/var`. You can override these on the command line or via `config.ru` for rack setups. (#16137, PR#1080) ## Changelog Josh Cooper (3) 88171aa Maint: Use pending block 33bf085 Maint: Make paths absolute on Windows 54acfba (#16137) Delay evaluation of config and var directories Andrew Parker (2) b53e600 (#16137) Tilde expansion should only occur for normal users 43590bd (Maint) Remove trailing whitespace Curtis Ruck (1) c0ff98d (#16137) Ensure HOME is set before attempting ~ expansion Genadi Samokovarov (1) 224d380 Move singleton require to puppet/util/storage.rb Eric Sorenson (1) 605e34d (#15739) Bump report_version since #10064 change its format Rahul (1) d834e76 (#6143) ensure that destroy works for zpools -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Announce: Puppet 2.7.19 Available
Hey Jo, You're totally right. Typo on my part, 2.7.19 is a final release, not a candidate. On Aug 23, 2012, at 11:36 AM, Jo Rhett wrote: On Aug 21, 2012, at 4:21 PM, Moses Mendoza wrote: Puppet 2.7.19 is a maintenance release candidate for Puppet in the Release, or release candidate? One of (version number, announcement) seems to be inconsistent. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 2.7.19 Available
Puppet 2.7.19 is a maintenance release candidate for Puppet in the 2.7.x series. It includes many bug fixes, including Windows improvements, Upstart service provider fixes, and several others. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.19.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.19.msi RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/puppet-2.7.19.dmg See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 2.7.19: http://projects.puppetlabs.com/projects/puppet/ This release contains contributions from Andrew Parker, Dustin J. Mitchell, Patrick Carlisle, Nick Lewis, Jakob Holy, R. Tyler Croy, Michael Stahnke, Josh Cooper, Moses Mendoza, Will Hopper, nfagerlund, Daniel Pittman, Ken Barber, Dominic Cleal, Stefan Shulte, Dominic Maraglia, Matthaus Litteken, Jeff McCune, Franz Pletz, Andy Sykes, and codec. This release does not address (#15561) regarding slashes in certnames. This remains a known issue. ## Puppet 2.7.19 Release Notes ## Ruby 1.9.3 has a different error when `require` fails. The text of the error message when load fails has changed, resulting in the test failing. This adapts that to catch the different versions, allowing this to pass in all cases. (#15291) Add Vendor tag to Puppet spec file Previously the spec file had no Vendor tag, which left it undefined. This commit adds a Vendor tag that references the _host_vendor macro, so that it can be easily set to 'Puppet Labs' internally and customized by users easily. The Vendor tag makes it easier for users to tell where the package came from. Add packaging support for fedora 17 This commit modifies the puppet.spec file to use the ruby vendorlib instead of sitelib if building for fedora 17, which ships with ruby 1.9. Mostly borrowed from the official Fedora 17 package. (#15471) Fix setting mode of last_run_summary The writlock function didn't work with setting the mode on the last_run_summary file. This backports some of the work in commit 7d8fd144949f21eff924602c2a6b7f130f1c0b69. Specifically, the changes from using writelock to replace_file for saving the summary file. This builds on top of the backport of getting replace_file to work on windows. (#15471) Ensure non-root can read report summary The security fix for locking down the last_run_report, which contains sensitive information, also locked down the last_run_summary, which does not contain sensitive information. Unfortunately this file is often used by monitoring systems so that they can track puppet runs. Since the agent runs as root and the monitoring systems do not, this caused the summary to become unreadable by the monitoring systems. This commit returns the summary to being world readable which undoes part of the change done in fd44bf5e6d0d360f6a493d663b653c121fa83c3f Use Win32 API atomic replace in `replace_file` The changes to enable Windows support in `replace_file` were not actually complete, and it didn't work when the file didn't exist - because of limitations of the emulation done on our side, rather than anything else. Windows has a bunch of quirks, and Ruby doesn't actually abstract over the underlying platform a great deal. We can use the Windows API ReplaceFile, and MoveFileEx, to achieve the desired behaviour though. This adds even more conditional code inside the `replace_file` method to handle multiple platforms - but it really isn't very clean. Better to get this working now, then refactor, though. (#11868) Use `Installer` automation interface to query package state Previously, Puppet recorded MSI packages it had installed in a YAML file. However, if the file was deleted or the system modified, e.g. Add/Remove Programs, then Puppet did not know the package state had changed. Also, if the name of the package did not change across versions, e.g. VMware Tools, then puppet would report the package as insync even though the installed version could be different than the one pointed to by the source parameter. Also, `msiexec.exe` returns non-zero exit codes when either the package requests a reboot (194), the system requires a reboot (3010), e.g. due to a locked file, or the system initiates a reboot (1641). This would cause puppet to think the install failed, and it would try to reinstall the packge the next time it ran (since the YAML file didn't get updated). This commit changes the msi package provider to use the `Installer` Autom
Re: [Puppet Users] Installing puppet agent on Windows XP
Hey Jeff, You can check out the release notes here: http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes . They're not split out by platform but rather Puppet version. Some of the Windows improvements I was thinking of, particularly around the package provider, are actually in the 2.7.19 RC, which, with any luck, will go final next week. However, as Adam points out, Windows XP isn't a supported platform, so your results may vary... On Thu, Aug 16, 2012 at 3:05 PM, Jeff Sussna wrote: > Grr...it would help if I were paying attention and didn't just assume the > list was sorted in most-recent order :-(. > > Since I don't seem to be able to find my way around unchaperoned, are there > release notes for the improvements you mention? > > > On Thursday, August 16, 2012 3:25:06 PM UTC-5, Moses Mendoza wrote: >> >> Hi Jeff, >> >> The latest stable msi is actually Puppet 2.7.18 - >> http://downloads.puppetlabs.com/windows/puppet-2.7.18.msi >> >> It includes many Windows improvements since 2.7.12. >> >> Cheers, >> Moses >> >> On Thu, Aug 16, 2012 at 12:34 PM, Jeff Sussna wrote: >> > OK, I tried again with the latest MSI >> > (http://downloads.puppetlabs.com/windows/puppet-2.7.12.msi) and puppet >> > and >> > facter both work just fine. Very cool! >> > >> > I should note that I'm running puppet in standalone mode, and not trying >> > to >> > connect to a master. >> > >> > On Monday, November 21, 2011 7:31:53 PM UTC-6, Jacob Helwig wrote: >> >> >> >> On 2011-11-21 12:50 , Jeff Sussna wrote: >> >> > Trying to get Puppet 2.7.6/Facter 1.6.2 running on Windows XP SP3. >> >> > Followed the install instructions carefully, got no errors. facter >> >> > and >> >> > puppet both hang no matter what I try. The only things that don't >> >> > hang >> >> > are: >> >> > >> >> > facter operatingsystem (or any other individual facter query) >> >> > facter --version >> >> > >> >> > facter --debug hangs, as does puppet --version or any other puppet >> >> > command, including 'puppet config print all'. >> >> > >> >> > Anyone have success getting puppet running on XP? >> >> > >> >> >> >> Right now, Puppet & Facter are only supported on Server 2003 & Server >> >> 2008, since those are the only platforms we tested against when working >> >> on the Windows support. If come up with patches to get past the hangs >> >> on XP we'd love to see them. >> >> >> >> Which install instructions were you following? If it didn't clearly >> >> call out which platforms are currently supported, we'll need to update >> >> the instructions. >> >> >> >> -- >> >> Jacob Helwig >> >> http://about.me/jhelwig >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Puppet Users" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/r8nCZFu-qU0J. >> > To post to this group, send email to puppet...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/DFtfU0zxdRQJ. > > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
