[Puppet Users] Re: Announce: 2.6.9 Released
Just wanted to follow up and say thanks for the improvement to the
release notes after the recent thread, much more useful now!
- Original Message -
= 2.6.9 =
2.6.9 is a maintenance release in the 2.6.x branch.
Notable Fixes and Features
Bug #7127:
A puppet run will now stop if a prerun command fails.
Bug #650
Puppet will now honor symlinks for configuration directories
Feature #2128
Added support for hostname setting based on facts, also get facts
before retrieving the catalog.
Bug #7139
Accept ‘/’ as a valid path in filesets
CHANGELOG
2.6.9
98ba407 (#7127) Stop puppet if a prerun command fails
6996e0b Do not needlessly create multiple reports when creating a
transaction
caca469 (#4416) Ensure types are providified after reloading
413b136 (#4416) Always remove old provider before recreating it
98f58ce (#2128) Add WARNING for node_name_{fact,value} descriptions
d9b5c1a (#2128) In-line docs for node_name_{fact,value}
3f0dbb5 (#650) Allow symlinks for configuration directories
1c70f0c (#2128) Add support for setting node name based on a fact
c629958 (#2128) Get facts before retrieving catalog
cd4fe14 (#2128) Add the ability to specify a node name
16b2311 (#6885) puppet agent fingerprint requires --verbose to return
a value.
75e2764 (#5318) Always notice changes to manifests when compiling.
8b76be3 (#3836) External nodes should only capture stdout
90eb937 (#7139) Accept '/' as a valid path in filesets
729336e (#6845) Mount writes incorrect vfstab entries
16cf1ac (#6442) Be able to start agents --listen without
namespaceauth.conf
0352402 (#3420) Nagios name attribute does not output correctly
f656818 (#4487) When setting environment on a host, ensure it is a
string.
c306db2 (#6487) Add some testing for OS X version support in
DirectoryService provider
0008b63 (#6487) Directoryservice provider will fail in future OS
releases
6b18f8f Move acceptance tests from puppet-acceptance repo
9a5bf6e Fixed #7166 - Replaced deprecated stomp send method with
publish
656eff8 (#4655) Allow stage to be set using a default class parameter
7f658e6 vim: Initial ftplugin and indent support
ccbe9f3 Fixed #6681 - Remove --force-yes option from aptitude is used
--
You received this message because you are subscribed to the Google
Groups Puppet Announce group.
To post to this group, send email to
puppet-annou...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-announce+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-announce?hl=en.
--
R.I.Pienaar
--
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] Re: PuppetCA not signing Certificate-Requests
Hey Denmat, I'm already using Passenger with Apache. Problem is still there. Markus On 20 Jun., 23:00, Denmat tu2bg...@gmail.com wrote: Hi, If you are using the standard webrick server that comes puppetmasterd then you will find it doesn't scale very well. Check out the scaling puppet docs on the puppetlabs site for your options. Cheers, Deb On 20/06/2011, at 22:18, markus markus.fenste...@googlemail.com wrote: I'm not sure whether it is a problem with the Provisioner I use. I added a little sleep time between requesting the node to send its CSR to the Server and the signing of this certificate on all nodes. Until now it works perfectly. On 18 Jun., 18:58, markus markus.fenste...@googlemail.com wrote: Hi! I'm having a setup with MCollective 1.2.0, Puppet 2.6.4 and an provision-agent. Most of the time this works great, but sometimes (every 10th node or so) I experience, that signing-requests of puppet- agents are not getting signed on the master. So the request of the puppet agent to /production/certificate/... ends everytime in an HTTP-Error 404. Does anyone have a glue about that? The problem is also hard to analyze because the logoutput is not very detailed. Puppet-Agent: Jun 18 16:10:38 ip-10-242-62-183 puppet-agent[1001]: Creating a new SSL key for ... Jun 18 16:10:38 ip-10-242-62-183 puppet-agent[1001]: Caching certificate for ca Jun 18 16:10:41 ip-10-242-62-183 puppet-agent[1001]: Creating a new SSL certificate request for ... Jun 18 16:10:41 ip-10-242-62-183 puppet-agent[1001]: Certificate Request fingerprint (md5): 6A:3F:63:8A:59:2C:F6:C9:5E:56:5F:39:16:FF: 19:BE Puppet-Master: puppet:443 a.b.c.d - - [18/Jun/2011:18:10:39 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:39 +0200] GET /production/ certificate_request/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:42 +0200] PUT /production/ certificate_request/a.b.c.d HTTP/1.1 200 2202 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:42 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:43 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:03 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:04 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:04 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:48 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:48 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - Regards Markus -- 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 athttp://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] Re: PuppetCA not signing Certificate-Requests
Puppet doesn't even recognise the CSR that was sended. Is there a known threading problem with puppetca? Or a problem, that it can not handle several requests per seconds to add and sign CSRs? On 22 Jun., 12:10, markus markus.fenste...@googlemail.com wrote: Hey Denmat, I'm already using Passenger with Apache. Problem is still there. Markus On 20 Jun., 23:00, Denmat tu2bg...@gmail.com wrote: Hi, If you are using the standard webrick server that comes puppetmasterd then you will find it doesn't scale very well. Check out the scaling puppet docs on the puppetlabs site for your options. Cheers, Deb On 20/06/2011, at 22:18, markus markus.fenste...@googlemail.com wrote: I'm not sure whether it is a problem with the Provisioner I use. I added a little sleep time between requesting the node to send its CSR to the Server and the signing of this certificate on all nodes. Until now it works perfectly. On 18 Jun., 18:58, markus markus.fenste...@googlemail.com wrote: Hi! I'm having a setup with MCollective 1.2.0, Puppet 2.6.4 and an provision-agent. Most of the time this works great, but sometimes (every 10th node or so) I experience, that signing-requests of puppet- agents are not getting signed on the master. So the request of the puppet agent to /production/certificate/... ends everytime in an HTTP-Error 404. Does anyone have a glue about that? The problem is also hard to analyze because the logoutput is not very detailed. Puppet-Agent: Jun 18 16:10:38 ip-10-242-62-183 puppet-agent[1001]: Creating a new SSL key for ... Jun 18 16:10:38 ip-10-242-62-183 puppet-agent[1001]: Caching certificate for ca Jun 18 16:10:41 ip-10-242-62-183 puppet-agent[1001]: Creating a new SSL certificate request for ... Jun 18 16:10:41 ip-10-242-62-183 puppet-agent[1001]: Certificate Request fingerprint (md5): 6A:3F:63:8A:59:2C:F6:C9:5E:56:5F:39:16:FF: 19:BE Puppet-Master: puppet:443 a.b.c.d - - [18/Jun/2011:18:10:39 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:39 +0200] GET /production/ certificate_request/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:42 +0200] PUT /production/ certificate_request/a.b.c.d HTTP/1.1 200 2202 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:42 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:10:43 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:03 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:04 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:04 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:26 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:48 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - puppet:443 a.b.c.d - - [18/Jun/2011:18:11:48 +0200] GET /production/ certificate/a.b.c.d HTTP/1.1 404 2298 - - Regards Markus -- 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 athttp://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] Re: Problem in wordpress moodule.
On Jun 20, 5:15 pm, lucas.brig...@ymail.com grillobri...@gmail.com
wrote:
I actually posted about the problem with tar.
I decided to modify the module to not depend on tar installed.
But I realized that any command that has parameters to run, the same problem
occurswhen using this command:
exec {$ tar-vzxf downdir} {wordpress.tar.gz
path = [/ usr / local / bin, / opt / local / bin, /
usr / bin, / usr / sbin]
}
The path in that command is broken: there should be no whitespace
around the slashes. That could easily be enough to make the Exec
fail. Beyond the whitespace problem, that path also does not contain
the standard (LSB) location of the tar command (/bin), which would
certainly make the Exec fail if you do not have a copy of tar or a
link to it in one of the directories you do specify. On the third
hand, the code you posted contains at least two syntax errors, so who
knows what you're really using.
But when I run for example:
exec {ps}
The error did not occur previously posted.
Here you are relying on the default path provided by Puppet, which is
not documented to work. The docs say that you should either use a
fully-qualified command (e.g. /bin/ps) or specify a search path that
can resolve the command (e.g. [ /bin, /usr/bin, /sbin, /usr/
sbin ]; note no whitespace in the directory names). I don't know
what Puppet provides as a default, but it must include /bin.
John
--
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: Problem in wordpress moodule.
These errors that you report was due to bad formatting of the text when
posted.
But thanks for the tips.
2011/6/22 jcbollinger john.bollin...@stjude.org
On Jun 20, 5:15 pm, lucas.brig...@ymail.com grillobri...@gmail.com
wrote:
I actually posted about the problem with tar.
I decided to modify the module to not depend on tar installed.
But I realized that any command that has parameters to run, the same
problem
occurswhen using this command:
exec {$ tar-vzxf downdir} {wordpress.tar.gz
path = [/ usr / local / bin, / opt / local / bin,
/
usr / bin, / usr / sbin]
}
The path in that command is broken: there should be no whitespace
around the slashes. That could easily be enough to make the Exec
fail. Beyond the whitespace problem, that path also does not contain
the standard (LSB) location of the tar command (/bin), which would
certainly make the Exec fail if you do not have a copy of tar or a
link to it in one of the directories you do specify. On the third
hand, the code you posted contains at least two syntax errors, so who
knows what you're really using.
But when I run for example:
exec {ps}
The error did not occur previously posted.
Here you are relying on the default path provided by Puppet, which is
not documented to work. The docs say that you should either use a
fully-qualified command (e.g. /bin/ps) or specify a search path that
can resolve the command (e.g. [ /bin, /usr/bin, /sbin, /usr/
sbin ]; note no whitespace in the directory names). I don't know
what Puppet provides as a default, but it must include /bin.
John
--
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.
--
Lucas Pereira Brígida
--
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] Re: Puppet Caching Problem
Upgrading to 2.6.8 and applying the patch worked for me! Thank you! On 20 Jun., 19:13, Daniel Pittman dan...@puppetlabs.com wrote: On Mon, Jun 20, 2011 at 05:11, markus markus.fenste...@googlemail.com wrote: I've got a MCollective Setup (1.2.0) with Puppet (2.6.4), an provision agent and an external node configuration script that fetches configurations from a database. Sometimes it happens, that puppet caches the configuration of the server and doesn't notice a change in the configuration. Odds are, no: I suspect that if you run the agent a second time you will have things work; 2.6.4 had a nasty bug that would cause the master to ignore changes to your manifests the first time you ran it after the file changed (and, theoretically, but never observed, more than once.) If you find that is the case, upgrading to 2.6.9 will fix things up, or you can dig up the patch set I posted to the list earlier; it should apply cleanly to 2.6.4 as a point-fix to get things working. (You only need to upgrade the *master* for this to be fixed; a 2.6.4 client will work fine.) Daniel -- ⎋ Puppet Labs Developer –http://puppetlabs.com ✉ Daniel Pittman dan...@puppetlabs.com ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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.0 Released
Hi, thanks for the new version, I was looking forward to it since puppetcamp A'dam... Just a minor issue: Installation from the gem gives a rdoc error (on Ubunu/RHEL with ruby 1.8.7): # gem install puppet -v 2.7.0 Successfully installed puppet-2.7.0 1 gem installed Installing ri documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a34b6a0) ... RDOC args: --ri --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/ri --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) Installing RDoc documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a928500) ... RDOC args: --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/rdoc --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) --- Thanks! Frederik On Tue, Jun 21, 2011 at 8:33 PM, Michael Stahnke stah...@puppetlabs.com wrote: It's here! Puppet 2.7.0. This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz It's available as a gem from rubygems.org. 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 2.7.0 http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes To see the Full CHANGELOG: https://raw.github.com/puppetlabs/puppet/2.7.0/CHANGELOG Puppet 2.7.0 is out! This is a major feature release, and there's a lot of new stuff. Here's the high-level version: Apache License --- Puppet is now released under the Apache 2.0 license. More info is available [here](http://docs.puppetlabs.com/guides/faq#change-to-apache-license). Ruby 1.9 Support There are some known issues with the 2.7.0 release, but YES: we are now supporting Ruby 1.9.2 and higher, and will be aggressively fixing bugs under Ruby 1.9! Deterministic Catalog Application --- Previously, Puppet didn't guarantee that it would apply unrelated resources in any particular order. This meant that if you forgot to specify some important `before` or `require` relationship, a single catalog might work fine on eight nodes and then fail mysteriously on the ninth and tenth. This could be frustrating! Now it's gone: Puppet will make sure that the same catalog will always be applied in the same order on every machine, and it'll either succeed reliably or fail reliably. (This change will also be appearing in the final 2.6.x releases.) Manage Network Devices Puppet has new types for managing network hardware, and a new `puppet device` subcommand for applying these configurations. These are in their early stages and can currently only handle Cisco hardware, but they're the start of a big leap forward in Puppet's ability to manage your entire infrastructure. Man Pages We've spiffed up our man pages, in both regular and on-the-fly flavors! Try `man puppet-agent` or `puppet man catalog`, and party like it's 1971. (We recommend running `gem install ronn` before using the `puppet man` subcommand.) New Subcommands and the Faces API - We've added a powerful new API for creating new Puppet subcommands, and we've used it to expose most of Puppet's internal subsystems. One of our devs has written a series of blog posts about it ([one][faceswhat], [two][facesmore], [three][facesthree]), and there's more documentation on the way, but this opens the door to whole new ways of running Puppet and exploiting its data. To get a look at the new subcommands, just run `puppet help`; if you're interested in tweaking Puppet under the hood, take a look at `lib/puppet/face/secret_agent.rb` to see how easy it is to re-implement the puppet agent application. We've also implemented a new help interface: just run `puppet help subcommand [action]` for short, to-the-point command-line help with the Faces
[Puppet Users] environment ENC vs cmdline
Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally production) is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment is already set in the ENC. The ENC environment settings seems to always win over the cmdline. Is the the desired behavior? I would like to set all configuration (incl. environment) in the ENC, but want to be able to override it from the cmdline. (BTW: switching the environment from the cmdline works, when I remove the line from the ENC.) Thanks and bye, Frederik -- 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.0 Released
Hi, My Puppet dashboard shows errors on nodes that want to upgrade from 2.6.7 to 2.7.0. Package[puppet] (/etc/puppet/production/modules/puppet/manifests/init.pp:24) Property Message ensure change from 2.6.7 to 2.7.0 failed: Could not update: Could not install: RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x9f7eff0) ... RDOC args: --ri --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/ri --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0xb4c3d0c) ... RDOC args: --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/rdoc --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) INFO: `gem install -y` is now default and will be removed INFO: use --ignore-dependencies to install only the gems you list Successfully installed puppet-2.7.0 1 gem installed Installing ri documentation for puppet-2.7.0... Installing RDoc documentation for puppet-2.7.0... at /etc/puppet/production/modules/puppet/manifests/init.pp:24 warning Skipping because of failed dependencies /Stage[main]/Puppet/File[puppet.conf] /etc/puppet/production/modules/puppet/manifests/init.pp 36 2011-06-22 14:55 CEST warning Skipping because of failed dependencies /Stage[main]/Puppet::Centos/Service[puppet] /etc/puppet/production/modules/puppet/manifests/centos.pp 29 2011-06-22 14:55 CEST When I check the local machine the gem was installed, but the service is not restarted so 2.7.0 is not being used. I have a cron job setup that reloads the deamon process once a week, but would like to use 2.7.0 right after upgrade. --- Martin 2011/6/22 Frederik Wagner fner...@googlemail.com Hi, thanks for the new version, I was looking forward to it since puppetcamp A'dam... Just a minor issue: Installation from the gem gives a rdoc error (on Ubunu/RHEL with ruby 1.8.7): # gem install puppet -v 2.7.0 Successfully installed puppet-2.7.0 1 gem installed Installing ri documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a34b6a0) ... RDOC args: --ri --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/ri --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) Installing RDoc documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a928500) ... RDOC args: --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/rdoc --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) --- Thanks! Frederik On Tue, Jun 21, 2011 at 8:33 PM, Michael Stahnke stah...@puppetlabs.com wrote: It's here! Puppet 2.7.0. This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz It's available as a gem from rubygems.org. 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 2.7.0 http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available:
Re: [Puppet Users] Using modules from PuppetForge
On Mon, Jun 20, 2011 at 10:38 AM, Kyle Hall kyle.m.h...@gmail.com wrote:
Hello All,
New puppet user here. I've been able to create and use my own puppet
modules, but I'm at a loss on how to use modules from PuppetForge,
which seem quite a bit more advanced. For example, I've installed the
camptocamp/apt module via the command 'puppet-module install
camptocamp/apt' into /etc/puppet/modules. I then tried to add the
following code to one of my manifests:
apt::sources_list {google-chrome:
ensure = present,
content = deb http://dl.google.com/linux/chrome/deb/
stable main,
}
apt::key {A040830F7FAC5991:
source =
https://dl-ssl.google.com/linux/linux_signing_key.pub;
}
package { 'google-chrome-stable' :
ensure = latest,
require = File['google-chrome-apt-repository'],
}
When I run the agent, I get an error stating that apt::sources_list is
an invalid resource type. Any idea what I'm doing wrong? I've spent
the last couple hours searching for an answer, and have yet to find
anything that spells it out.
Kyle,
You're not doing anything wrong, the utility is.
The currently released version of the puppet-module tool has a bug
where the module installed doesn't itself follow Puppet's autoloader
conventions.
You'll have /etc/puppet/modules/camptocamp-apt, but Puppet's
autoloader is expecting the module to live at /etc/puppet/modules/apt
You can simply move the module into the correct place.
I've also just fixed this bug a couple of days ago and it will do the
right thing in the next release.
--
Jeff McCune
Puppet Labs
@0xEFF
--
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] Re: Ruby 1.9.2 - puppetd error Could not request certificate: SSL_connect returned=1
I was having the same problem on a very similar setup. My fix was to put a 'hashed' link in the openssl certs directory to the CA certificate on the agent machine. So you if you haven't already copied your ca.pem or ca_crt.pem file to the agent host, that is your first step. openssl version -d [will give you give you base openssl dir] openssl x509 -hash -noout -in /etc/puppet/ssl/certs/ca.pem [will give you CA cert hash...something like 520f3686] go into the openssl dir you received from above and create a 'hashed' link in the certs directory to your CA cert file. ls -al /etc/pki/tls/certs/520f3686.0 lrwxrwxrwx 1 root root 29 Jun 22 02:21 /etc/pki/tls/certs/520f3686.0 - /etc/puppet/ssl/ca/ca_crt.pem Note that a .0 is added the end of your hash when creating the link. On Jun 15, 12:32 pm, EduardR edrozenb...@gmail.com wrote: Hello, Running latest Puppet 2.7rc4, Ruby 1.9.2 p180, slackware 13.37 64. Default (webrick) setup, no mongrel no apache. Running puppet master on the main puppet server works fine, no problem. Running puppet agent on the same machine works fine, no problem. Running puppet agent on a client server (separate machine) connecting to master gives the following error: err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed I found this post that suggests the error could be related to ruby 1.9 not finding a cert file to use:http://martinottenwaelter.fr/2010/12/ruby19-and-the-ssl-error/ The problem comes from the fact that the new Ruby 1.9 installation doesn’t find the certification authority certificates (CA Certs) used to verify the authenticity of secured web servers. However, I've had no luck despite trying to add SSL_CERT_FILE and SSL_CERT_PATH env variables to default.rb and puppet agent command line. If the cert file is the problem, is there some other way to get puppet to pass the proper cert info to ruby (my system certs are in / etc/ssl/certs) ? If I use Ruby 1.8.7, no problem. I'd prefer to use 1.9.x though, since it comes with my distro and some other software uses 1.9. Also, if I use ruby 1.8.7 to register my client, then upgrade everything to ruby 1.9, the agent works (presumably because the certificate setup is already complete). Thanks in advance, --Ed -- 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] Using modules from PuppetForge
Excellent. I was able to figure that out eventually. Thanks for the reply!
Kyle
http://www.kylehall.info
Mill Run Technology Solutions ( http://millruntech.com )
Crawford County Federated Library System ( http://www.ccfls.org )
Meadville Public Library ( http://www.meadvillelibrary.org )
On Wed, Jun 22, 2011 at 11:04 AM, Jeff McCune j...@puppetlabs.com wrote:
On Mon, Jun 20, 2011 at 10:38 AM, Kyle Hall kyle.m.h...@gmail.com wrote:
Hello All,
New puppet user here. I've been able to create and use my own puppet
modules, but I'm at a loss on how to use modules from PuppetForge,
which seem quite a bit more advanced. For example, I've installed the
camptocamp/apt module via the command 'puppet-module install
camptocamp/apt' into /etc/puppet/modules. I then tried to add the
following code to one of my manifests:
apt::sources_list {google-chrome:
ensure = present,
content = deb http://dl.google.com/linux/chrome/deb/
stable main,
}
apt::key {A040830F7FAC5991:
source =
https://dl-ssl.google.com/linux/linux_signing_key.pub;
}
package { 'google-chrome-stable' :
ensure = latest,
require = File['google-chrome-apt-repository'],
}
When I run the agent, I get an error stating that apt::sources_list is
an invalid resource type. Any idea what I'm doing wrong? I've spent
the last couple hours searching for an answer, and have yet to find
anything that spells it out.
Kyle,
You're not doing anything wrong, the utility is.
The currently released version of the puppet-module tool has a bug
where the module installed doesn't itself follow Puppet's autoloader
conventions.
You'll have /etc/puppet/modules/camptocamp-apt, but Puppet's
autoloader is expecting the module to live at /etc/puppet/modules/apt
You can simply move the module into the correct place.
I've also just fixed this bug a couple of days ago and it will do the
right thing in the next release.
--
Jeff McCune
Puppet Labs
@0xEFF
--
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] Can no longer sync files with Puppet
Hello All,
I'm just starting with puppet and I've run into an issue I cannot
figure out. I'm trying to sync the home directory for a user from a
home directory stored on my puppet server. Here is my manifest code:
user { public:
ensure = present,
shell = '/bin/bash',
home = '/home/public',
managehome = true,
password = 'chestnut',
}
file { public-home:
path= '/home/public',
ensure = directory,
owner = 'public',
group = 'public',
recurse = true,
replace = true,
purge = true,
ignore = '.git',
source = 'puppet:///files/users/home/public',
require = User['public'],
}
The files are stored in /etc/puppet/files/users/home/public
What is really strange is that it was working fine, except that it
appeared that the replace and purge options were not working. Then,
after a few test runs, I started seeing this error:
err: Could not run Puppet configuration client: Error 400 on SERVER:
Not authorized to call find on /file_metadata/files/users/home/public
at /etc/puppet/manifests/public-base.pp:58
Any ideas? I tried chmod'ing the files directory on the server to 777,
but that did not help. I've moved the file around a few times trying
different things without success. If I comment out the file section,
my catalog runs just fine.
Thanks,
Kyle
http://www.kylehall.info
Mill Run Technology Solutions ( http://millruntech.com )
Crawford County Federated Library System ( http://www.ccfls.org )
Meadville Public Library ( http://www.meadvillelibrary.org )
--
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] Re: Can no longer sync files with Puppet
I think I solved my problem. I changed my fileserver.conf from:
# This file consists of arbitrarily named sections/modules
# defining where files are served from and to whom
# Define a section 'files'
# Adapt the allow/deny settings to your needs. Order
# for allow/deny does not matter, allow always takes precedence
# over deny
[files]
path /etc/puppet/files
# allow *.example.com
# deny *.evil.example.com
# allow 192.168.0.0/24
[plugins]
# allow *.example.com
# deny *.evil.example.com
# allow 192.168.0.0/24
to
# This file consists of arbitrarily named sections/modules
# defining where files are served from and to whom
# Define a section 'files'
# Adapt the allow/deny settings to your needs. Order
# for allow/deny does not matter, allow always takes precedence
# over deny
[files]
path /etc/puppet/files
allow *
# allow *.example.com
# deny *.evil.example.com
# allow 192.168.0.0/24
[modules]
allow *
[plugins]
allow *
# allow *.example.com
# deny *.evil.example.com
# allow 192.168.0.0/24
and now everything works! I still have no idea why this error starting
appearing.
Kyle
http://www.kylehall.info
Mill Run Technology Solutions ( http://millruntech.com )
Crawford County Federated Library System ( http://www.ccfls.org )
Meadville Public Library ( http://www.meadvillelibrary.org )
On Wed, Jun 22, 2011 at 11:29 AM, Kyle Hall kyle.m.h...@gmail.com wrote:
Hello All,
I'm just starting with puppet and I've run into an issue I cannot
figure out. I'm trying to sync the home directory for a user from a
home directory stored on my puppet server. Here is my manifest code:
user { public:
ensure = present,
shell = '/bin/bash',
home = '/home/public',
managehome = true,
password = 'chestnut',
}
file { public-home:
path = '/home/public',
ensure = directory,
owner = 'public',
group = 'public',
recurse = true,
replace = true,
purge = true,
ignore = '.git',
source = 'puppet:///files/users/home/public',
require = User['public'],
}
The files are stored in /etc/puppet/files/users/home/public
What is really strange is that it was working fine, except that it
appeared that the replace and purge options were not working. Then,
after a few test runs, I started seeing this error:
err: Could not run Puppet configuration client: Error 400 on SERVER:
Not authorized to call find on /file_metadata/files/users/home/public
at /etc/puppet/manifests/public-base.pp:58
Any ideas? I tried chmod'ing the files directory on the server to 777,
but that did not help. I've moved the file around a few times trying
different things without success. If I comment out the file section,
my catalog runs just fine.
Thanks,
Kyle
http://www.kylehall.info
Mill Run Technology Solutions ( http://millruntech.com )
Crawford County Federated Library System ( http://www.ccfls.org )
Meadville Public Library ( http://www.meadvillelibrary.org )
--
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] environment ENC vs cmdline
On Wed, Jun 22, 2011 at 7:15 AM, Frederik Wagner fner...@googlemail.comwrote: Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally production) is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment is already set in the ENC. The ENC environment settings seems to always win over the cmdline. Is the the desired behavior? It is, but there are some complications as this bug shows: http://projects.puppetlabs.com/issues/3910 I would like to set all configuration (incl. environment) in the ENC, but want to be able to override it from the cmdline. (BTW: switching the environment from the cmdline works, when I remove the line from the ENC.) The plan is to allow the client-specified environment to be exposed to the ENC, and then in your ENC you can make the choice between using that, or specifying an environment centrally. Thanks and bye, Frederik -- 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. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- 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] Extlookup and stages
Hi, I've seen some weird behaviour using extlookup, and wondered if anyone has seen it too... Basically it seems that if the $extlookup_* variables are defined in site.pp then an early stage use of extlookup doesn't see these variables at all, yet main stage ones do. I added some debug statements to extlookup.rb and just printed the vars, and they didn't exist. moving the lines into my template.pp which site.pp just includes they then are there and extlookup works fine. If I leave both declarations in both files then they clash, so clearly they are being loaded, but not at the right time?? Currently i've just left the declarations in templates.pp however the docs explicitly state putting them in site.pp so something is awry... Any info appreciated. Thanks Chris -- 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] gentoo linux and puppet
Hi folks, I am building a server using Gentoo Linux and was about to start automating the package loads using puppet. First things first I loaded the latest and greatest facter and puppet from gems. Got the new SSL certificate loaded and ran puppetd --test and expected to see a base manifest loaded. Instead here is how it went: puppetd --test err: Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Eh? Never saw that before... -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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.0 Released
Hi Martin, On Wed, Jun 22, 2011 at 4:52 PM, Martin Willemsma mwillem...@gmail.com wrote: My Puppet dashboard shows errors on nodes that want to upgrade from 2.6.7 to 2.7.0. (snip) warning Skipping because of failed dependencies /Stage[main]/Puppet/File[puppet.conf] /etc/puppet/production/modules/puppet/manifests/init.pp 36 2011-06-22 14:55 CEST warning Skipping because of failed dependencies /Stage[main]/Puppet::Centos/Service[puppet] /etc/puppet/production/modules/puppet/manifests/centos.pp 29 2011-06-22 14:55 CEST When I check the local machine the gem was installed, but the service is not restarted so 2.7.0 is not being used. If I get it right, your dependent service is not restarting, since the upgrade resource fails? For me it worked just installing the gem 2.7.0 next to 2.6.8 (through the package provider). How would you have the package provider installing/updateing the puppet gem trigger the puppet service, without killing the just running (daemonized/scheduled) puppet process? It works in two runs: 1. install/upgrade the gem, triggering the service restart (which happens, so the new puppet version is running, but the current run got killed). 2. the next scheduled run, runs normally with the new version. But is there a way not to have the running process killed and produce a failed run? BTW: How do I uninstall the old gem? (there is no ensure = ^2.6.8 or similar) Bye Fredeirk I have a cron job setup that reloads the deamon process once a week, but would like to use 2.7.0 right after upgrade. --- Martin 2011/6/22 Frederik Wagner fner...@googlemail.com Hi, thanks for the new version, I was looking forward to it since puppetcamp A'dam... Just a minor issue: Installation from the gem gives a rdoc error (on Ubunu/RHEL with ruby 1.8.7): # gem install puppet -v 2.7.0 Successfully installed puppet-2.7.0 1 gem installed Installing ri documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a34b6a0) ... RDOC args: --ri --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/ri --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) Installing RDoc documentation for puppet-2.7.0... RDoc failure in lib/puppet/interface/option.rb at or around line 6 column 40 Before reporting this, could you check that the file you're documenting compiles cleanly--RDoc is not a full Ruby parser, and gets confused easily if fed invalid programs. The internal error was: ERROR: While generating documentation for puppet-2.7.0 ... MESSAGE: Name or symbol expected (got #RubyToken::TkDSTRING:0x7f734a928500) ... RDOC args: --op /usr/lib/ruby/gems/1.8/doc/puppet-2.7.0/rdoc --title Puppet - Configuration Management --main README --line-numbers --quiet lib --title puppet-2.7.0 Documentation (continuing with the rest of the installation) --- Thanks! Frederik On Tue, Jun 21, 2011 at 8:33 PM, Michael Stahnke stah...@puppetlabs.com wrote: It's here! Puppet 2.7.0. This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz It's available as a gem from rubygems.org. 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 2.7.0 http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes To see the Full CHANGELOG: https://raw.github.com/puppetlabs/puppet/2.7.0/CHANGELOG Puppet 2.7.0 is out! This is a major feature release, and there's a lot of new stuff. Here's the high-level version: Apache License --- Puppet is now released under the Apache 2.0 license. More info is available [here](http://docs.puppetlabs.com/guides/faq#change-to-apache-license). Ruby 1.9 Support There are some known issues with the 2.7.0 release, but YES: we are now supporting Ruby 1.9.2 and higher, and will be aggressively fixing bugs under Ruby 1.9! Deterministic Catalog Application --- Previously, Puppet didn't guarantee that it would apply unrelated resources in any particular order. This meant that if you forgot to specify some important `before` or `require` relationship, a single
Re: [Puppet Users] environment ENC vs cmdline
Hi Nigel, ah yes, thanks. I think I just ran into the problem people were mentioning at puppetcamp... oops. Now I finally get it ;-) Thanks, Frederik On Wed, Jun 22, 2011 at 7:08 PM, Nigel Kersten ni...@puppetlabs.com wrote: On Wed, Jun 22, 2011 at 7:15 AM, Frederik Wagner fner...@googlemail.com wrote: Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally production) is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment is already set in the ENC. The ENC environment settings seems to always win over the cmdline. Is the the desired behavior? It is, but there are some complications as this bug shows: http://projects.puppetlabs.com/issues/3910 I would like to set all configuration (incl. environment) in the ENC, but want to be able to override it from the cmdline. (BTW: switching the environment from the cmdline works, when I remove the line from the ENC.) The plan is to allow the client-specified environment to be exposed to the ENC, and then in your ENC you can make the choice between using that, or specifying an environment centrally. -- 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] need help with name parameter
Hi, A bit of help is needed with this geppetto issue: https://github.com/cloudsmith/geppetto/issues/87 It is about the parameter name in relation to file. Appreciate feedback. Regards - henrik -- 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] Re: ANNOUNCE: Puppet 2.7.0 Released
For the item: Notice Changed Manifests on the First Try --- During the 2.6.x series, puppet agent would sometimes require two runs to receive new configurations when puppet master was running under Passenger. This persistent bug has been dealt with. (This change will also be appearing in the final 2.6.x releases.) Was this addressed in 2.6.9 release? It says it will be in the final 2.6.x releases, and on the 2.6.9 announcement page it says This will likely be the last release in the 2.6.x series for Puppet, now that 2.7 is out. but I'm not sure which bug addressed under 2.6.9 would be this issue. Thanks, Jake On Jun 21, 1:33 pm, Michael Stahnke stah...@puppetlabs.com wrote: It's here! Puppet 2.7.0. This release is available for download at:http://puppetlabs.com/downloads/puppet/puppet-2.7.0.tar.gz It's available as a gem from rubygems.org. 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 2.7.0http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available:https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes To see the Full CHANGELOG:https://raw.github.com/puppetlabs/puppet/2.7.0/CHANGELOG Puppet 2.7.0 is out! This is a major feature release, and there's a lot of new stuff. Here's the high-level version: Apache License --- Puppet is now released under the Apache 2.0 license. More info is available [here](http://docs.puppetlabs.com/guides/faq#change-to-apache-license). Ruby 1.9 Support There are some known issues with the 2.7.0 release, but YES: we are now supporting Ruby 1.9.2 and higher, and will be aggressively fixing bugs under Ruby 1.9! Deterministic Catalog Application --- Previously, Puppet didn't guarantee that it would apply unrelated resources in any particular order. This meant that if you forgot to specify some important `before` or `require` relationship, a single catalog might work fine on eight nodes and then fail mysteriously on the ninth and tenth. This could be frustrating! Now it's gone: Puppet will make sure that the same catalog will always be applied in the same order on every machine, and it'll either succeed reliably or fail reliably. (This change will also be appearing in the final 2.6.x releases.) Manage Network Devices Puppet has new types for managing network hardware, and a new `puppet device` subcommand for applying these configurations. These are in their early stages and can currently only handle Cisco hardware, but they're the start of a big leap forward in Puppet's ability to manage your entire infrastructure. Man Pages We've spiffed up our man pages, in both regular and on-the-fly flavors! Try `man puppet-agent` or `puppet man catalog`, and party like it's 1971. (We recommend running `gem install ronn` before using the `puppet man` subcommand.) New Subcommands and the Faces API - We've added a powerful new API for creating new Puppet subcommands, and we've used it to expose most of Puppet's internal subsystems. One of our devs has written a series of blog posts about it ([one][faceswhat], [two][facesmore], [three][facesthree]), and there's more documentation on the way, but this opens the door to whole new ways of running Puppet and exploiting its data. To get a look at the new subcommands, just run `puppet help`; if you're interested in tweaking Puppet under the hood, take a look at `lib/puppet/face/secret_agent.rb` to see how easy it is to re-implement the puppet agent application. We've also implemented a new help interface: just run `puppet help subcommand [action]` for short, to-the-point command-line help with the Faces subcommands. [facesthree]:http://www.puppetlabs.com/blog/about-faces-until-we-go-in-the-right-d... [faceswhat]:http://www.puppetlabs.com/blog/puppet-faces-what-the-heck-are-faces/ [facesmore]:http://www.puppetlabs.com/blog/faces-actions-options-and-facades-oh-my/ Deprecations -- We're starting the hourglass on a few older features: * **'puppet' as a synonym for 'puppet apply'** --- Starting today, running `puppet my-manifest.pp` will issue a warning; you should start using `puppet apply` directly instead. Support for implicit invocation of puppet apply will be dropped in Puppet 2.8. * **Dynamic scope** --- We've started issuing warnings when variables or resource defaults are found via dynamic lookup. [There's more info and explanation in a guide on the docs site](http://docs.puppetlabs.com/guides/scope_and_puppet.html), but the short version is that you should start referencing variables with their qualified names instead of counting on dynamic scope. We hope to drop support for dynamic scope in Puppet 2.8. * **No more `--parseonly` option** --- This one's already gone, because we used
[Puppet Users] Dashboard LDAP ENC's
puppet 2.6.8 I have been going over and over 'Pro Puppet' book and http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes /etc/puppet/puppet.conf includes in the [master] section: node_terminus = ldap ldapserver = ubuntu.ttinet ldapbase = ou=Hosts,dc=ttinet,dc=local and LDAP contains the below (derived from an ldapsearch) # andromeda.ttinet, Hosts, ttinet.local dn: cn=andromeda.ttinet,ou=Hosts,dc=ttinet,dc=local cn: andromeda.ttinet description: Andromeda objectClass: device objectClass: top objectClass: puppetClient objectClass: ipHost ipHostNumber: VALID_LOCAL_IP puppetClass: base environment: production I've restarted both puppetmaster and apache (Dashboard is running on passenger) and still, I don't see the above system in 'Nodes' though I haven't run or even installed puppet on that system. Shouldn't it show up in Dashboard as a node that has never reported? I'm trying to figure out how to get Dashboard to import the ENC 'nodes' from LDAP. Logs don't show any errors and I do have ruby-ldap installed... # ruby -rldap -e puts :installed installed -- Craig White ~~ craig.wh...@ttiltd.com 1.800.869.6908 ~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- 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 2.7.0 Released
On Wed, Jun 22, 2011 at 11:00, Jake - USPS jacob.m.mcc...@usps.gov wrote: For the item: Notice Changed Manifests on the First Try --- During the 2.6.x series, puppet agent would sometimes require two runs to receive new configurations when puppet master was running under Passenger. This persistent bug has been dealt with. (This change will also be appearing in the final 2.6.x releases.) Was this addressed in 2.6.9 release? Yes, this was part of the 2.6.9 release; the bug is #5318, and it went in before we cut that release. (Note, though, that this only matters on the Puppet Master, so even if it hadn't, running a 2.7 master with 2.6 clients would have fixed the bug. :) Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman dan...@puppetlabs.com ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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] need help with name parameter
So it would appear the parameter 'name' acts as namevar for file and
exec at least ... its not defined in the type for these explicitly -
it seems implicit. This seems historical and I haven't seen it used
before (at least I've never used it myself). Does anyone know the
history behind this?
The following:
@key_attribute_parameters ||= (
params = @parameters.find_all { |param|
param.isnamevar? or param.name == :name
}
)
Is defined in puppet/type.rb :-). Not sure if we have this behavior
documented - or if its up for deprecation :-).
ken.
On Wed, Jun 22, 2011 at 6:40 PM, Henrik Lindberg
henrik.lindb...@cloudsmith.com wrote:
Hi,
A bit of help is needed with this geppetto issue:
https://github.com/cloudsmith/geppetto/issues/87
It is about the parameter name in relation to file.
Appreciate feedback.
Regards
- henrik
--
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.
buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
Hello... On Mon, 2011-06-20 at 10:48 -0400, Todd Zullinger wrote: snip Better late than never, I've pushed rpm's for this release to my fedorapeople.org repo: http://tmz.fedorapeople.org/repo/puppet/ Packages for EL 4 - 6 and Fedora 13 - 15 are available for testing. Add the puppet.repo file from either the epel or fedora directories to /etc/yum.repos.d to enable. If you find problems with the packaging, please let me know. If you find other bugs, please file them in redmine: http://projects.puppetlabs.com/projects/puppet/issues I don't know if this is a rpm buglet or a general puppet buglet, but with puppet-2.6.9-0.1.rc1.el5.noarch.rpm from tmz I get emails like: Wed Jun 22 12:46:11 -0700 2011 Puppet (notice): Finished catalog run in 6.53 seconds on every run. I haven't tested the final release as I am going to test 2.7.0 with ruby 1.9.2 instead. Please note that 2.6.6 is in Fedora and EPEL testing repositories. I don't plan to update puppet there until 2.6.6 is pushed to the stable updates repos. Any help testing the 2.6.6 packages is most welcome. Once that update is stable, we'll be better able to more closely track the 2.6.x updates in the official repos. -- Christopher McCrory To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the engineer, the glass is twice as big as it needs to be. -- 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: buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available
Hi, Christopher McCrory wrote: I don't know if this is a rpm buglet or a general puppet buglet, but with puppet-2.6.9-0.1.rc1.el5.noarch.rpm from tmz I get emails like: Wed Jun 22 12:46:11 -0700 2011 Puppet (notice): Finished catalog run in 6.53 seconds on every run. I haven't tested the final release as I am going to test 2.7.0 with ruby 1.9.2 instead. Is this different than with 2.6.8? This is definitely not something caused by the packaging, so if it's changed for the worse in some way, you'd want to file it in the puppetlabs.com issue tracker. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ The nice thing about egotists is that they don't talk about other people. -- Lucille S. Harper pgpKMhJTCn6RU.pgp Description: PGP signature
[Puppet Users] custom facts not propagating
Hi I have puppet client 0.25.5 running on about 100 solaris 8 servers and only two of them gets the custom facts. My puppet master is 2.6.8 running ubuntu lucid Here are my custom facts $ cat /etc/puppet/modules/common/lib/facter/bash.rb Facter.add(bash) do setcode do bash = `which bash`.chomp bash = /bin/sh if bash.empty? bash end end Facter.add(zonename) do setcode do zonename = `zonename`.chomp zonename = global if zonename.empty? zonename end end $ cat /etc/puppet/puppet.conf [main] pluginsync = true factsync = true logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter:$confdir/modules/common/lib/facter templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post [master] # These are needed when the puppetmaster is run by passenger # and can safely be removed if webrick is used. ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY reports = http, store, tagmail # for remote site reporturl = http://dashboard.example.net:9000/reports node_terminus = exec external_nodes = /usr/local/bin/external.sh Here is my puppet.conf on all the puppet clients $ cat /etc/puppet/puppet.conf splay = true report = true pluginsync = true syslogfacility = local0 I have a simple class that shows the $bash and $zonename facts are empty for all but those two puppet clients in the notice() Any way to debug why custom facts are propagating? -- 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.
[Puppet Users] apt-key and untrusted packages
Perhaps this is a Debian/Ubuntu question and not a puppet problem but... Seems as though the key is good but the install failed. # apt-key list /etc/apt/trusted.gpg --- snip --- pub 2048R/7F0CEB10 2010-02-05 uid Richard Kreuter rich...@10gen.com and the 7F0CEF10 key (10gen) is the key in question anyway, puppet failed to install the package and running the install from the command line, I can sort of see why... # apt-get install mongodb-10gen Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ssl-cert Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: mongodb-10gen 0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 27.3MB of archives. After this operation, 70.6MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! mongodb-10gen Install these packages without verification [y/N]? n E: Some packages could not be authenticated puppet of course stumbles with the same problem... # puppet agent --test --verbose --ignorecache --server ubuntu.ttinet info: Retrieving plugin info: Loading facts in datacenter info: Loading facts in datacenter info: Caching catalog for ubuntu2.ttinet info: Applying configuration version '1308777226' err: /Stage[main]/Mongodb/Package[mongodb-10gen]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install mongodb-10gen' returned 100: Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: ssl-cert Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: mongodb-10gen 0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 27.3MB of archives. After this operation, 70.6MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! mongodb-10gen E: There are problems and -y was used without --force-yes err: /Stage[main]/Mongodb/Service[mongodb]/ensure: change from stopped to running failed: Could not find init script for 'mongodb' notice: Finished catalog run in 1.06 seconds and you can imagine that I am not very keen on automating anything with --force ?? -- Craig White ~~ craig.wh...@ttiltd.com 1.800.869.6908 ~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- 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] Using require and notify across class resources cause a dependency cycle
I have a simple sample below that illustrates a problem I ran into
today. What I am trying do is execute a command only if another
class, that which is dependent on it's class, triggers the command
with a notify. I'm using the refreshonly = true to prevent it from
running unless something triggers it. The require is needed because
other things need to be done in class a before class b.
When I run this code I get the following error message:
err: Could not apply complete catalog: Found dependency cycles in the
following relationships
Am I doing something wrong?
I think my only solution is to move the Exec[a] out of class a but I
would think that this should work...
Thanks,
John
class a {
exec { 'a':
command = 'echo This is a test file and can be deleted
(Exec[a]) /tmp/puppet-test2.txt',
refreshonly = true,
}
# some other commands
}
class b {
file { '/tmp/puppet-test1.txt':
content = 'This is a test file and can be deleted (File)',
require = Exec['a'],
notify = Exec['a']
}
}
include a
include b
--
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 2.7.0 Released
I've been able to reproduce this issue and we'll have a fixed gem out shortly. Mike -- 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] undefined method error when installing Puppet Dashboard 1.1.1
I've never installed Puppet Dashboard before but it seemed straightforward. I'm installing v1.1.1 on Ubuntu 11.04 with Ruby 1.8.7 and with Puppetmaster v2.6.4. The rake creation step appears to succeed: prompt rake RAILS_ENV=production db:create But when I try to migrate: prompt rake RAILS_ENV=production db:migrate it exits with the error: undefined method `name' for activemodel:String Any clues? J -- 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] exporting resources that aren't built-in resources...
We seem to be able to export resources (and import them) just fine if they are basic resources, like nagios_* -- but we don't seem to be able to do it with defines, like @@concat::fragment. $ puppet -V 2.6.4 Is this a bug? Intended behavior? Are we doing something wrong? -- 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] Re: exporting resources that aren't built-in resources...
On Wed, Jun 22, 2011 at 3:03 PM, Rich Rauenzahn rraue...@gmail.com wrote: We seem to be able to export resources (and import them) just fine if they are basic resources, like nagios_* -- but we don't seem to be able to do it with defines, like @@concat::fragment. $ puppet -V 2.6.4 Is this a bug? Intended behavior? Are we doing something wrong? ugh. We were only using a single not a . nevermind Rich -- 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 Subreddit
Just letting everyone know that this subreddit exists. http://www.reddit.com/r/puppet Enjoy, -Joe -- 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.1
2.7.1 is a bug fix release in the 2.7.x branch. Fixing bug #8048. This made users of Puppet as a gem unable to install Puppet 2.7.0 release if gem was configured to use rdoc, as rdoc failed to parse on one file. This issue only impacted users of Puppet as a gem. - This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.7.1.tar.gz It's available as a gem from rubygems.org. 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 2.7.1 http://projects.puppetlabs.com/projects/puppet/ Full Release Notes are available: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes To see the Full CHANGELOG: https://raw.github.com/puppetlabs/puppet/2.7.1/CHANGELOG -- 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] How to manage many nodes easily?
These is another question, i have many defines which will apply an
application to sepcified path, called as:
application::add { app1: path = /var/app1 }
by this i can apply app1 and app2 in node1, app3 and app4 in node2, etc.
now, how do i switch this to a class? Need i create a seperate class for all
the apps although the only difference is the path?
2011/6/21 Chris Phillips ch...@untrepid.com
I would see a principle whereby nodes should not ever be defined within
the manifest code at all. To me the manifests should be written to be very
generic, and then use ENC's to modify their behaviour at a user level.
There is still a lot of inconsistency within Puppet as to how device
specific data can be obtained (extlookup is very useful but rides roughshod
over other architectural principles) but I try to stick to keeping all
manifests generic. I write manifests to manage a package, then create a
group in dashboard to relate that function to a business need and then a
node into that group.
On 21 June 2011 14:48, Martin Willemsma mwillem...@gmail.com wrote:
We use /etc/puppet/node-definitions/*.pp in site.pp similar to what Carles
is saying.
[node-definitions] is a git repo thats being synced on both puppermasters.
This happens on every push to origin
We use the 'default' node which does the baseline configuration based on a
'role'
In a separate file $fqdn.pp I place the definitions for a node.
Are there more people using this kind of approach?
---
Martin
2011/6/21 Carles Amigó carles.am...@softonic.com
We had the same problem and we just separated each node (or group of
nodes) in one file and then we load them using the following syntax:
import nodes/*.pp
You could also organize those files in subdirectories if you like so:
import nodes/*/*.pp
The only problem we've found with this approach is when creating new
files, puppetmaster takes a while to see them.
El 20/06/2011 5:25, flex escribió:
We have many modules and many nodes, every node may use different
module, so it's very unpleasant to modify the nodes.pp
Then i saw the external node, but seems it only support class and we
have many defines called in node.pp
So here is my question: Is there another way for us to manage so many
nodes easily or should i change all the defines to classes and using
external nodes?
--
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+unsubscribe@*
*googlegroups.com puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/puppet-users?hl=enhttp://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.
--
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.
--
System Administrator, Focus on System Management and Basic Development
--
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] facter + ssh = tput errors
Hi Guys, Not sure if this issue is a facter one or not, but thought i might post here to see if anyone else has had the same issue. When executing facter command on remote ssh server, i am getting tput errors. However when running any other command on this same remote ssh server, the tput errors do not occur. [user@server1 ~]$ ssh server2 'facter hostname' tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified server2 If i run facter locally on the remote server, there are no tput errors. [user@server2 ~]$ facter hostname server2 In googling the errors, there are a lot of recommendations to check profile scripts, etc, but the errors only occur with facter via ssh, not any other commands and i can't see any references to tput in the profile scripts? Does anyone have any ideas as to what could be causing this issue and how to fix? -- 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] apt-key and untrusted packages
On 06/22/2011 11:29 PM, Craig White wrote: Perhaps this is a Debian/Ubuntu question and not a puppet problem but... Seems as though the key is good but the install failed. # apt-key list /etc/apt/trusted.gpg --- snip --- pub 2048R/7F0CEB10 2010-02-05 uid Richard Kreuter rich...@10gen.com and the 7F0CEF10 key (10gen) is the key in question anyway, puppet failed to install the package and running the install from the command line, I can sort of see why... You need to run apt-get update after import of the key. apt-get install will read from local cache which still has no information regarding the key. # apt-get install mongodb-10gen Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ssl-cert Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: mongodb-10gen 0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 27.3MB of archives. After this operation, 70.6MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! mongodb-10gen Install these packages without verification [y/N]? n E: Some packages could not be authenticated puppet of course stumbles with the same problem... # puppet agent --test --verbose --ignorecache --server ubuntu.ttinet info: Retrieving plugin info: Loading facts in datacenter info: Loading facts in datacenter info: Caching catalog for ubuntu2.ttinet info: Applying configuration version '1308777226' err: /Stage[main]/Mongodb/Package[mongodb-10gen]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install mongodb-10gen' returned 100: Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: ssl-cert Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: mongodb-10gen 0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded. Need to get 27.3MB of archives. After this operation, 70.6MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! mongodb-10gen E: There are problems and -y was used without --force-yes err: /Stage[main]/Mongodb/Service[mongodb]/ensure: change from stopped to running failed: Could not find init script for 'mongodb' notice: Finished catalog run in 1.06 seconds and you can imagine that I am not very keen on automating anything with --force ?? -- 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] How to manage many nodes easily?
On 06/23/2011 04:35 AM, flex wrote:
These is another question, i have many defines which will apply an
application to sepcified path, called as:
application::add { app1: path = /var/app1 }
by this i can apply app1 and app2 in node1, app3 and app4 in node2, etc.
now, how do i switch this to a class? Need i create a seperate class for
all the apps although the only difference is the path?
You can make use of parameterized classes:
class application::add($appname) {
path = '/var/${appname}',
...
}
Within your node definition you call the class with desired parameter:
node 'node1' {
class application::add { appname = 'app1' }
class application::add { appname = 'app3' }
}
Kind regards,
Martin
2011/6/21 Chris Phillips ch...@untrepid.com mailto:ch...@untrepid.com
I would see a principle whereby nodes should not ever be defined
within the manifest code at all. To me the manifests should be
written to be very generic, and then use ENC's to modify their
behaviour at a user level. There is still a lot of inconsistency
within Puppet as to how device specific data can be obtained
(extlookup is very useful but rides roughshod over other
architectural principles) but I try to stick to keeping all
manifests generic. I write manifests to manage a package, then
create a group in dashboard to relate that function to a business
need and then a node into that group.
On 21 June 2011 14:48, Martin Willemsma mwillem...@gmail.com
mailto:mwillem...@gmail.com wrote:
We use /etc/puppet/node-definitions/*.pp in site.pp similar to
what Carles is saying.
[node-definitions] is a git repo thats being synced on both
puppermasters. This happens on every push to origin
We use the 'default' node which does the baseline configuration
based on a 'role'
In a separate file $fqdn.pp I place the definitions for a node.
Are there more people using this kind of approach?
---
Martin
2011/6/21 Carles Amigó carles.am...@softonic.com
mailto:carles.am...@softonic.com
We had the same problem and we just separated each node (or
group of nodes) in one file and then we load them using the
following syntax:
import nodes/*.pp
You could also organize those files in subdirectories if you
like so:
import nodes/*/*.pp
The only problem we've found with this approach is when
creating new files, puppetmaster takes a while to see them.
El 20/06/2011 5:25, flex escribió:
We have many modules and many nodes, every node may use
different
module, so it's very unpleasant to modify the nodes.pp
Then i saw the external node, but seems it only support
class and we
have many defines called in node.pp
So here is my question: Is there another way for us to
manage so many
nodes easily or should i change all the defines to
classes and using
external nodes?
--
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
mailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@__googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/__group/puppet-users?hl=en
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
mailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
mailto: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
mailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at
[Puppet Users] Re: How to manage many nodes easily?
On Jun 23, 7:44 am, Martin Alfke tux...@gmail.com wrote:
On 06/23/2011 04:35 AM, flex wrote:
These is another question, i have many defines which will apply an
application to sepcified path, called as:
application::add { app1: path = /var/app1 }
by this i can apply app1 and app2 in node1, app3 and app4 in node2, etc.
now, how do i switch this to a class? Need i create a seperate class for
all the apps although the only difference is the path?
You can make use of parameterized classes:
class application::add($appname) {
path = '/var/${appname}',
...
}
Within your node definition you call the class with desired parameter:
node 'node1' {
class application::add { appname = 'app1' }
class application::add { appname = 'app3' }
}
The mentioned usage of parameterized classes in node definition is
wrong.
See: http://docs.puppetlabs.com/guides/language_guide.html#parameterised-classes
node 'node1' {
class { 'application::app': appname = 'app1' }
class { 'application::add': appname = 'app3' }
}
Kind regards,
Martin
2011/6/21 Chris Phillips ch...@untrepid.com mailto:ch...@untrepid.com
I would see a principle whereby nodes should not ever be defined
within the manifest code at all. To me the manifests should be
written to be very generic, and then use ENC's to modify their
behaviour at a user level. There is still a lot of inconsistency
within Puppet as to how device specific data can be obtained
(extlookup is very useful but rides roughshod over other
architectural principles) but I try to stick to keeping all
manifests generic. I write manifests to manage a package, then
create a group in dashboard to relate that function to a business
need and then a node into that group.
On 21 June 2011 14:48, Martin Willemsma mwillem...@gmail.com
mailto:mwillem...@gmail.com wrote:
We use /etc/puppet/node-definitions/*.pp in site.pp similar to
what Carles is saying.
[node-definitions] is a git repo thats being synced on both
puppermasters. This happens on every push to origin
We use the 'default' node which does the baseline configuration
based on a 'role'
In a separate file $fqdn.pp I place the definitions for a node.
Are there more people using this kind of approach?
---
Martin
2011/6/21 Carles Amig� carles.am...@softonic.com
mailto:carles.am...@softonic.com
We had the same problem and we just separated each node (or
group of nodes) in one file and then we load them using the
following syntax:
import nodes/*.pp
You could also organize those files in subdirectories if you
like so:
import nodes/*/*.pp
The only problem we've found with this approach is when
creating new files, puppetmaster takes a while to see them.
El 20/06/2011 5:25, flex escribi�:
We have many modules and many nodes, every node may use
different
module, so it's very unpleasant to modify the nodes.pp
Then i saw the external node, but seems it only support
class and we
have many defines called in node.pp
So here is my question: Is there another way for us to
manage so many
nodes easily or should i change all the defines to
classes and using
external nodes?
--
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
mailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@__googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/__group/puppet-users?hl=en
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
mailto:puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
mailto: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
