Re: [Puppet Users] Re: Remove certificate requests
I've been testing Razor and ended up with a bunch of requests from test machines that I didn't sign and didn't need any more. puppet cert print again fails because there's no certificate, only a request. Anyway, to answer my own question, I just needed to remove the requests from the puppet/ssl/ca/requests directory. Tim. On Fri, Dec 14, 2012 at 04:53:42PM -0800, Ellison Marks wrote: You might try puppet cert print to get more info about the thing, but out of curiosity, how did it get on your master in the first place? On Friday, December 14, 2012 1:14:54 PM UTC-8, Tim Bishop wrote: Nope: puppetmaster# puppet cert list fb311ff01c6f0130b650005056bc6664 (SHA256) FB:E2:F1:86:5D:80:74:25:35:75:3D:09:8F:1E:41:0B:15:D2:66:01:F2:F1:B3:4E:6D:5B:F9:85:4B:BC:AC:28 puppetmaster# puppet cert clean fb311ff01c6f0130b650005056bc6664 Error: Could not find a serial number for fb311ff01c6f0130b650005056bc6664 Looks like it only cleans signed certificates, not requests. On Fri, Dec 14, 2012 at 10:33:30AM -0800, Ellison Marks wrote: Does puppet cert clean not do it? On Friday, December 14, 2012 9:43:12 AM UTC-8, Tim Bishop wrote: I've got some certificate requests on my puppet master that I wish to remove. It looks like the puppet cert tool doesn't have an option for doing that? What's the best approach, just manually remove them from the puppet/ssl/ca/requests directory? -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 -- 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] Run stages frustration
Hi There,
I do a similar thing with my environment, I apply a class called applysoe
to all nodes that is responsible for applying my modules and classes to
nodes in a specific order as the ENC i use didn't initially support it.
Have you looked at the foreman ?
The imminent release of 1.1 supports param classes, and it could be of use
to you, there is a good video showing how these new actions work here:
http://www.youtube.com/watch?v=Ksr0tilbmcc
I havent tested it for run stages support however.
Hope this is of some use.
K
On Friday, December 14, 2012 9:40:15 PM UTC, Jakov Sosic wrote:
On 12/14/2012 09:52 PM, Jakov Sosic wrote:
Hi.
I am wondering why can't run stages get set inside the class?
For example:
class foo {
stage main
}
Because, if I want to use stages, I have to declare my class as
parametrized = so I can't use include or require anywhere else...
I thought of a different approach, like:
class foo_wrapper {
class{ 'foo': stage = 'somestage' }
}
but would it work if I later include/require foo_wrapper in more than
one place? And is this code ok?
OK, so it seems that stuff work when I declare it like this:
class foo {
stage {'beforemain': before = Stage['main'] }
}
class foo::def::a {
class { 'foo::classdef::a': stage = 'beforemain' }
}
class foo::def::b {
class { 'foo::classdef::b': stage = 'beforemain' }
}
class foo::classdef::a {
require foo::classdef::b
}
class foo::classdef::b {
}
I will try clean deploy of one of the systems to see if things break on
runtime, but this is surely very complex way of avoiding what seems to
be puppet limitation... It would be much easier if I could just set
stage somehow without wrapper class and resource-like declaration...
--
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/-/q5aK73M8hUAJ.
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: Catalog compile times 40s - Puppet 2.7.18
On Sunday, December 9, 2012 1:41:34 PM UTC-6, treydock wrote:
I am finding that the puppetlabs-apache module is somehow adding 30-60
seconds onto a host's catalog compile time when the puppetmaster has no
other hosts contacting or generating catalogs. The Puppetmaster is setup
to use Puppet-2.7.18 - Apache Passenger. RIght now only 2 hosts are even
configured to use this new PM, the PM itself and a Foreman host. With
neither hosts contacting the PM, and disabling the include apache and
require apache::mod::dev in puppetlabs-passenger, I get Config
retrieval: 2.45.
Catalogs had hostnames replaced, puppetmaster.tld is the CNAME for Puppet
master and puppetmaster-host.tld is the actual hostname.
Catalog: http://pastebin.com/V29JmB8J
# puppet agent --{summarize,test,debug,evaltrace,noop} | perl -pe
's/^/localtime().: /e'
snip
Sun Dec 9 13:05:35 2012: notice: Finished catalog run in 2.43 seconds
Sun Dec 9 13:05:35 2012: Changes:
Sun Dec 9 13:05:35 2012: Events:
Sun Dec 9 13:05:35 2012: Total: 1
Sun Dec 9 13:05:35 2012: Noop: 1
Sun Dec 9 13:05:35 2012: Resources:
Sun Dec 9 13:05:35 2012: Out of sync: 1
Sun Dec 9 13:05:35 2012: Total: 22
Sun Dec 9 13:05:35 2012: Skipped: 6
Sun Dec 9 13:05:35 2012: Time:
Sun Dec 9 13:05:35 2012: Resources: 0.00
Sun Dec 9 13:05:35 2012:Filebucket: 0.00
Sun Dec 9 13:05:35 2012: Package: 0.00
Sun Dec 9 13:05:35 2012: File: 0.00
Sun Dec 9 13:05:35 2012: Firewall: 0.01
Sun Dec 9 13:05:35 2012: Exec: 0.14
Sun Dec 9 13:05:35 2012: Last run: 1355079935
Sun Dec 9 13:05:35 2012:Config retrieval: 2.45
Sun Dec 9 13:05:35 2012: Total: 2.61
Sun Dec 9 13:05:35 2012: Version:
Sun Dec 9 13:05:35 2012:Config: 1355077701
Sun Dec 9 13:05:35 2012:Puppet: 2.7.18
Uncommenting include apache and require apache::mod::dev in
puppetlabs-passenger about 40 seconds are added to the compile time. I
went through disabled all modules and parameters, and found that enabling
the passenger module alone with Apache included caused the huge delay.
Catalog: http://pastebin.com/wwcKgX5b
# puppet agent --{summarize,test,debug,evaltrace,noop} | perl -pe
's/^/localtime().: /e'
snip
Sun Dec 9 13:13:08 2012: notice: Finished catalog run in 2.23 seconds
Sun Dec 9 13:13:08 2012: Changes:
Sun Dec 9 13:13:08 2012: Events:
Sun Dec 9 13:13:08 2012: Total: 4
Sun Dec 9 13:13:08 2012: Noop: 4
Sun Dec 9 13:13:08 2012: Resources:
Sun Dec 9 13:13:08 2012: Out of sync: 4
Sun Dec 9 13:13:08 2012: Skipped: 6
Sun Dec 9 13:13:08 2012: Total: 80
Sun Dec 9 13:13:08 2012: Time:
Sun Dec 9 13:13:08 2012:Filebucket: 0.00
Sun Dec 9 13:13:08 2012: Resources: 0.00
Sun Dec 9 13:13:08 2012: Package: 0.00
Sun Dec 9 13:13:08 2012: Firewall: 0.01
Sun Dec 9 13:13:08 2012: File: 0.01
Sun Dec 9 13:13:08 2012: A2mod: 0.03
Sun Dec 9 13:13:08 2012: Service: 0.07
Sun Dec 9 13:13:08 2012: Exec: 0.14
Sun Dec 9 13:13:08 2012: Last run: 1355080388
Sun Dec 9 13:13:08 2012:Config retrieval: 42.79
Sun Dec 9 13:13:08 2012: Total: 43.06
Sun Dec 9 13:13:08 2012: Version:
Sun Dec 9 13:13:08 2012:Config: 1355080261
Sun Dec 9 13:13:08 2012:Puppet: 2.7.18
The install is via RPM. I'm using the Fedora SRPMs rebuilt for CentOS 6.
The Puppet master has two environments, development and production with
this as the puppet.conf
# cat /etc/puppet/puppet.conf
---
[main]
server= puppetmaster.tld
logdir= /var/log/puppet
vardir= /var/lib/puppet
ssldir= /var/lib/puppet/ssl
rundir= /var/run/puppet
factpath = $vardir/lib/facter
pluginsync= true
templatedir = $confdir/templates
[agent]
report = true
environment = production
preferred_serialization_format = yaml
[master]
modulepath=
/etc/puppet/environments/$environment/modules:/etc/puppet/modules
manifest = /etc/puppet/manifests/site.pp
environment = production
autosign = false
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
certname = puppetmaster.tld
dns_alt_names = puppetmaster.tld,puppetmaster-host.tld
report= true
reports = store
#reports = store, foreman
[production]
manifest = /etc/puppet/manifests/site.pp
Has anyone run into this issue with puppetlabs-apache or know why my
compile times are so long? I have a
Re: [Puppet Users] New Puppet User: Issues with pre-commit script
On Fri, Dec 14, 2012 at 5:42 PM, Jagga Soorma jagg...@gmail.com wrote: Thanks for your reply Matthew. I changed that line to the following: /usr/bin/puppet parser validate $tmpfile /tmp/puppet-val.log 21 Here is what the log is capturing (problem with the environment?): -- simran@shinda:/var/tmp/puppet/puppet/manifests$ svn ci -m 'testing' nodes.pp ..snip.. Sendingnodes.pp Transmitting file data .svn: Commit failed (details follow): svn: Commit blocked by pre-commit hook (exit code 1) with output: Puppet syntax error in manifests/nodes.pp [root@ssfpuppetd01 hooks]# cat /tmp/puppet-val.log Error: Could not intialize global default settings: couldn't find HOME environment -- expanding `~/.puppet' OK. Subversion calls hook scripts with an empty environment for security reasons. See http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html#svn.reposadmin.create.hooks. So, your hook script is going to have to set HOME itself. Regards, Matt. -- 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] Package not installed
I'm trying to install a package with puppet, libxp6. I have installed many other packages this way, however for this particular package the result is aptitude search libxp6 p libxp6 - X Printing Extension (Xprint) client libra i A libxp6:i386 - X Printing Extension (Xprint) client libra p libxp6-dbg - X Printing Extension (Xprint) client libra p libxp6-dbg:i386 - X Printing Extension (Xprint) client libra I've looked in the puppet log files, and the package seems to be handled, however it seems to be skip any processing. Arnold Skimminge -- 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/-/na3HQ97YHw4J. 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] New Puppet User: Issues with pre-commit script
On 12/14/2012 03:00 AM, Jagga Soorma wrote: Hi Guys, I am new to puppet so please let me know if this is not the correct place for asking this question. I am setting up a new puppet environment running the latest 3.x version. I have the puppet master and client setup correctly and tested with deploying a simple file to the client. Now, I am working on adding all the configs to SVN since I will have all my users checkout the nodes.pp file and place their node entries in this file via SVN. I would like to do some check on this file before it is checked in to make sure there are no syntax errors. I am using the following pre-commit scirpt that I came across online: Take a look at my precommit script and modify it to suit SVN... You will need puppet rubygem-puppet-lint to get it to work: http://kosjenka.srce.hr/~jsosic/puppet/check_puppet.rb -- Jakov Sosic www.srce.unizg.hr -- 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 Dashboard for Rails 3
On 12/11/2012 12:33 AM, Aaron Stone wrote: Update: thanks to help from GitHub users @igreg and @astratto, Puppet Dashboard Rails 3 is now fully compatible with Ruby 1.9! The rails3 and rails3-aaa branches are up to date as of Dashboard version 1.2.15 plus the work on those branches. I'm down to just 3 test failures, and actively working on getting to fully clean test runs. Help appreciated! Please take a look at the test results from these Travis builds: https://travis-ci.org/sodabrew/puppet-dashboard/builds/3588533 Still working on the audit trail, but no new updates on that yet. Keep up the good work! I've never used dashboard, is there any demo? :) -- Jakov Sosic www.srce.unizg.hr -- 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] Managing puppet as Application software management
On 12/02/2012 07:43 AM, Dhaval wrote: Hi, using puppet can i manage application packages, for example if some application user want to install his application package, is it possible to maintain that package using puppet ? like opsware do ? Don't do you expect people on puppet mailing list to know what 'like opsware' means... I doubt many people here used or even read about opsware. So it would be a good point to describe what do you really want? What does 'like opsware' behaviour represent? -- Jakov Sosic www.srce.unizg.hr -- 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] Strange issue with create_resources and exec 'command' parameter
On 12/05/2012 01:17 AM, Gary Larizza wrote:
$stuff = { '/bin/false' = { 'command' = /bin/echo 'hello there' } }
create_resources('exec', $stuff)
Doesn't work here, puppet 3.0.1, rhel6...
# puppet apply test.pp
Error: /bin/false returned 1 instead of one of [0]
Error: /Stage[main]//Exec[/bin/false]/returns: change from notrun to 0
failed: /bin/false returned 1 instead of one of [0]
Finished catalog run in 0.16 seconds
--
Jakov Sosic
www.srce.unizg.hr
--
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: puppetlabs-firewall source array not working as expected
On 12/04/2012 03:56 PM, Terry Z. wrote: I believe you have stumbled into the same issue I ran into when attempting to workaround this with defined resources and unfortunately I had to continue using the legacy bobsh-iptables module as a result (which has its own inherent issues but at least properly accepts an array in source.) It is rather disheartening to see the puppet-firewall module stuck with these limitations, but I do understand the difficulty in making this work as we expect so it's a trade off. It's really not that hard to code array support to custom provider, has anyone tried it? Maybe if community can fix it, puppetlabs would accept pull request? -- Jakov Sosic www.srce.unizg.hr -- 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] Question on modeling multiple services sharing configuration
Hi!
I would appreciate any advice on the best practices
on how to model a collection of services that each
has its own configuration file, but also share a common
one.
Now, the trouble is, that the common configuration file
is not *really* just a place for the common configuration
to reside, but also may have sections dedicated to holding
properties of a particular service (just like /etc/puppet/puppet.conf
has [main] [agent] and [master] sections).
Thus, in reality, the configuration properties are
per service and whether they need to go into a common
configuration file or a service-specific one is NOT cleanly
partitioned and is pretty awkward to remember. Which
means I really don't want to expose the common config
explicitly to the end user.
Instead, I'd like to expose the natural hierarchy of:
class service1($foo, $bar, $baz) {
}
.
class serviceN($qoo, $zoo) {
}
but the question then becomes -- how can I model a
common configuration file behind user's back so that
$foo, $bar and $qoo end up there.
At first I was thinking that I could utilize a singleton
non-parameterized class and include it multiple
times in all of the serviceX class definitions, but it
seems I can't pass any values into it.
I suppose I can still do that and create a skeleton
of the common config in that singleton class
that would later be manipulated either by augeas or
concat patterns, but this seems to be pretty heavyweight.
What would you, guys, recommend?
Thanks,
Roman.
--
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] Managing puppet as Application software management
Sorry for the top posting. Perhaps are you searching for something like puppy by example42 ? Give it a look. Best 2012/12/2, Dhaval d.josh...@gmail.com: Hi, using puppet can i manage application packages, for example if some application user want to install his application package, is it possible to maintain that package using puppet ? like opsware do ? Regards, Dha -- 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/-/Qsd-H_T70vYJ. 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. -- Inviato dal mio dispositivo mobile -- 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: err: Could not request certificate: stack level too deep
On Saturday, September 15, 2012 6:10:33 AM UTC-7, quanta wrote: debug: Using cached certificate for ca err: Could not request certificate: stack level too deep debug: Using cached certificate for ca debug: Using cached certificate for ca /usr/lib/ruby/1.8/sync.rb:58:in `Fail': Thread(#Thread:0x2af83efcd378 run) not locked. (Sync_m::Err::UnknownLocker) from /usr/lib/ruby/1.8/sync.rb:64:in `Fail' from /usr/lib/ruby/1.8/sync.rb:184:in `sync_unlock' from /usr/lib/ruby/1.8/sync.rb:232:in `synchronize' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:650:in `uninterpolated_value' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:800:in `each_source' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:797:in `each' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:797:in `each_source' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:647:in `uninterpolated_value' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:646:in `catch' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:646:in `uninterpolated_value' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:682:in `value' from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:21:in `[]' from /usr/lib/ruby/site_ruby/1.8/puppet.rb:65:in `[]' from /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:297:in `wait_for_cert' from /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:407:in `setup_host' from /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:425:in `setup_agent' from /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:484:in `setup' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in `run' from /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute' from /usr/bin/puppet:4 Since I'm not familiar with Ruby, could you help me please to solve this? I had what I think is the same thing hit me today. looks like in newer puppet agent's if you only have the client cert local but not the CA.pem you get this obtuse error: Error: Could not request certificate: stack level too deep And if I add debug I get the trace like above. solution was to add ca.pem in the bundle I unpack during system initialization. Very frustrating nothing in release notes and other docs that I have been able to find on this change. The number of tools I have been bumping into recently that really heavily on certs but don't tend to manage/deal with them well -- 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/-/PoDJ1EimHLcJ. 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.
