I'm testing a 'cleanup' stage which runs after Stage[main] and removes a bunch
of package resources.
To do this, I tried a simple check of defined(Package[]) combined with a
custom facter fact (called 'app_packages'):
> class app::package::cleaner {
>
> define check_and_remove {
> if !de
We are also having this similar issue with v2.7.10.1. Short term fix is
deleting the lockfile that hasn't updated in 2x{puppet-run-cycle} and
restarting puppet.
On Tuesday, February 10, 2009 2:25:53 AM UTC-8, Keith Edmunds wrote:
>
> I'm just starting a roll out of Puppet and I'm seeing a prob
Need some assistance with what I believe is a requirement that can be
solved using Exported Resources (or maybe there is another method which is
better suited).
I have a module svn::server::init. This module can be called with a
parameter is_master which defines whether it is a master SVN serve
There's a third way, too. In the defined type's definition:
define software::mydefinedtype {
include software
Package['software'] -> Software::Mydefinedtype[$title]
...
...etc.
}
That creates a relationship between the package and every resource in each
instance of the defined type. Ever
I got mine solved...on puppet labs enterprise edition..
On each Client which is not connecting right …giving that error on puppet
agent -t
cd /etc/puppetlabs/puppet/ ssl
rm -rf ca certs public_keys certificate_requsts private_keys # make sure
all files removed from SSL dir
puppet ag
Here is what I have:
Essentially I use the command line tools instead of ruby functions.
This tells me exactly where the problem is down to the line number.
+1 for checking the erb files, I'll have to add that to my script.
I have the json check for my hieradata since I keep hiera in JSON for
On Monday, May 13, 2013 3:56:02 PM UTC-4, LTH wrote:
>
> We have several servers using various environments. However we have
> noticed when a server requests any of the non-production environments, that
> the production environment's last access time still changes along with the
> specific envi
PuppetDB 1.3.2 is now available for download! This is a very minor
compatibility release for the 1.3 series of PuppetDB.
===
## Downloads ##
===
Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Puppet module:
http://forge.pup
Hi Alexandra,
Attempt 2 is on the right track.
The thing to keep in mind here is that the package and service types both
rely on the platform's own naming conventions, so you'll often have to do a
bit of research when you're first starting to automate a new service or
whatever. In this case,
Hi all,
I have started with puppet recently and the intention is to manage network
devices, for now I'm working with a switch (cisco catalyst 2950) and trying
to configure ports.
I installed puppet following the installation guide on puppetlabs.com
OS: CentOS 6
Services running: puppetmaster &
Attempt 2 is on the right track. What OS are you on and what error messages
in particular are you running into?
On Monday, June 3, 2013 9:17:35 AM UTC-7, Alexandra Ferguson wrote:
>
> Fellow Puppet Users,
>
> I was assigned to learn how puppet works to integrate it into our
> department and I
Thanks, that solved the ssl problem.
Andy
On Friday, May 31, 2013 4:36:04 PM UTC-5, gen...@allantgroup.com wrote:
>
> When I run
>
> openssl s_client -host puppet -port 8081 -CAfile
> /etc/puppet/ssl/certs/puppet.fqdn
>
> I get Verify return code: 21 (unable to verify the first certificate).
>
Fellow Puppet Users,
I was assigned to learn how puppet works to integrate it into our
department and I am trying to go through the tutorial. I am a beginner in
IT work and am slowly starting to understand these processes. Right now I
am stuck on the last part of the Manifests tutorial, found
On Saturday, June 1, 2013 1:59:36 PM UTC-6, Stefan Schulte wrote:
>
> On Fri, 31 May 2013 15:56:30 -0700 (PDT)
> Marek Dohojda > wrote:
>
> > Having weird issue that I can't seem to find any solution to:
> >
> > puppet 2.7.21 and 2.6.9
> >
> > here is my stanza: ssh_authorized_key{ �$name
On 03/06/13 04:30 AM, Marc wrote:
> *Type 2:*
>
> /puppet-master[6246]: Dynamic lookup of $apache_ldap_auth is deprecated.
> For more information,
> see http://docs.puppetlabs.com/guides/scope_and_puppet.html. To see the
> change in behavior, use the --debug flag./
> /
> /
> As you can see, type
I am running puppet 3.2.1, using the puppetlabs repos, on centos 6.4. I
keep getting these messages in the log: (every 30 minutes)
Jun 3 11:24:55 yoda puppet-master[20292]: Failed to set SELinux context
system_u:object_r:puppet_etc_t:s0 on /etc/puppet/auth.conf
Jun 3 11:24:55 yoda puppet-maste
Seems like to me the SSL loaded into PuppetDB (the port 8081 you
mention) is not valid.
A simple activity would be to use our provided tool to reload the
certificates again:
* Move /etc/puppetdb/ssl to ssl.bak to preserve the original
* Backup /etc/puppetdb/conf.d/jetty.ini to say jetty.ini.bak t
> "Implement database, database_user, and database_grant provider"
> https://github.com/puppetlabs/puppetlabs-postgresql/issues/27
>
> The bug has been closed and that's a little unsatisfying.
> database, database_user and database_grant are resources internal
> to puppet, but only puppetlabs-m
Hi folks,
I've been staring for a long time now at this issue in the
PostgreSQL puppet module, discussing whether to
"Implement database, database_user, and database_grant provider"
https://github.com/puppetlabs/puppetlabs-postgresql/issues/27
The bug has been closed and that's a little un
On Sun, Jun 2, 2013 at 9:21 PM, Francisco Reyes wrote:
>
> Is there a way to list all the available modules? Or basically anything in
> the git repository should be able to be installed that way?
>
Well, your best bet is actually to flip over from using git to the forge.
http://forge.puppetlabs.c
Sorry, this is a repost of an earlier topic; I couldn't find the earlier
post so I thought it had not made it. I'm new to Google groups.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails f
Hello all.
I am modifying puppet code in order to make it puppet v3 compliant.
Currently I am running puppet 2.7.
When it comes to deprecation warnings I got 2 different types.
*Type 1:*
*puppet-master[6426]: Dynamic lookup of $apache_port at
/etc/puppet/environments/production/modules/apache/m
I have a test puppet installation on CentOS 6.4, version 3.2.1, all
uptodate with the puppetlabs repos. It is running the puppet master, a
puppet agent, dashboard, with foreman installed but not yet configured.
Part of the install for dashboard is copying the puppet_dashboard.rb file
to the /va
I am currently using puppet in testing, on a centos 6.4 machine running
puppet-master, puppet-agent, dashboard, and foreman. The manifest for the
puppet matser machine in empty, like so:
node 'puppet' {
}
However, when the pupper agent runs, it always deleted the dashboard report
module, whic
On Fri, 31 May 2013 07:52:25 -0700
Nan Liu wrote:
> A bit off topic, but you should use file attribute replace => false
> instead of an exec.
Indeed. I'm not sure how I've missed that parameter. And it seems to
have existed for a loong time. Thanks a lot for correcting me!
Matthias
--
Thanks for your ideas Trevor,
Looking at the current types and providers I could see some different ways
to do the same so I will give them a look during this week. As soon as I
have a working solution I will give feedback for others to work with.
Regards,
On Thursday, May 30, 2013 4:25:49 PM
Hi, thanks for your answer.
On Thursday, May 30, 2013 3:13:45 PM UTC+2, jcbollinger wrote:
>
>
> For this particular pattern of requirements, I strongly prefer method 1.
> It keeps everything associated directly with the defined type together in
> one place. I would suggest one tweak, however:
27 matches
Mail list logo
