Hi,
Is it possible to inhibit notify message on per resource basis?
For example, we use the fog library and it needs the AWS credentials
to be in /root/.fog
If we manage this file from puppet and anything changes, the
credentials will remain in the reports and we don't want this.
Can we stop th
On 03 Mar 2014, at 13:32, Cristian Falcas wrote:
> Hi,
>
> Is it possible to inhibit notify message on per resource basis?
>
> For example, we use the fog library and it needs the AWS credentials
> to be in /root/.fog
>
> If we manage this file from puppet and anything changes, the
> credenti
Hi,
I've created a simple class for creating/updating a file in a user's
home directory on Windows like so:
class put_file ($user = undef, $group = undef) {
file { 'user_dir':
path => "C:/Users/${user}",
ensure => directory,
owner => "${user}",
}
file { 'some_file':
path
Hi,
I'd like to keep symlinks to my manifests in
/etc/puppet/environments/common//manifests/, and have my real
manifests reside elsewhere, so that I can organize the real ones in
subdirectories as I prefer, e.g. under a CVS tree with an organization
based on project or else.
Unfortunately, it
Hey Moses
I'm still experiencing the same problems with puppet checking in as
'localhost' after waking form sleep. Any ideas what could be causing this?
The clients are either running vers. 3.4.2 or 3.4.3.
Any other troubleshooting suggestions?
Cheers
Phil
On Friday, February 14, 2014 7:36:44
Hi,
here is what I'm trying to do:
I want to be able to exclude certain hostnames/ from a module by passing
their hostnames in a parameter (array) within this module.
Example:
class centos-default {
class { 'module':
exclude => [ 'host1', 'host2' ],
}
class { 'module2':
exclude
I'm running into this as well. While it seems to be a rare error, Google
returns at least a few incidents of people with similar problems. Since I
doubt that this is a desired behavior, I'll call it a bug from this point.
I hit this bug when trying to install "The Foreman" via their official
Puppet Dashboard is listing a node as unresponsive for several days. But
the agent has been running twice an hour with no errors, and a manual run
of the agent shows it runs fine.
I cannot ping it with mcollective, and a query for disabled agents doesn't
list it.
I looked in the logs on the no
Could this be due to this bug? http://projects.puppetlabs.com/issues/8603
On Monday, March 3, 2014 4:04:56 PM UTC, Robert Rothenberg wrote:
>
> Puppet Dashboard is listing a node as unresponsive for several days. But
> the agent has been running twice an hour with no errors, and a manual run
> o
I'm standing up a Foreman front end for open source Puppet server. Every
Linux box seems to be working and checking in just fine. The problem child
is Windows 2012 R2. I can manually trigger an update with:
puppet agent --test
However, if I just let it sit there, it'll never check back in. A
Well, that was just ignorance on my part. I have followed instructions
at https://github.com/mosen/puppet-plist and now I'm up and running. This
provider has the ability to use either CFPropertyList or PlistBuddy for
plist modification.
--
You received this message because you are subscribed
On Saturday, March 1, 2014 9:40:57 AM UTC-6, Jeff Bachtel wrote:
>
> While implementing restart is good, if for some reason you were unable to
> do that you need only set *hasrestart => false* for the service resource,
> per http://docs.puppetlabs.com/references/latest/type.html#service . That
On Friday, February 28, 2014 9:33:41 AM UTC-6, Jason Hatman wrote:
>
> I've been looking all over for usage examples for CFPropertyList. I'm
> trying to make a test manifest to create a simple plist and it keeps saying
> that it can't find class CFPropertyList. I downloaded the zip from
> htt
You are comparing a string (hostname) with an array.
Instead of != you should use something like:
If ! $::hostname in $exclude
Regards,
El 03/03/2014 16:33, "cko" escribió:
> Hi,
> here is what I'm trying to do:
>
> I want to be able to exclude certain hostnames/ from a module by passing
> the
We're currently arguing^w discussing the use of the params class in
conjunction with hiera lookups and we've arrived at what I think is a
pretty good pattern. Let me explain by way of example, using the venerable
ntp application
class ntp{
include ::ntp::params
Class['::ntp::params']->
cl
We could have been talking in my cube. My points when I'm discussing this with
coworkers generally go like so...
If you use this:
class { name: }
You will only be able to declare that name once. If you declare classes like
this:
include ::name
include ::name::otherclass
Then you will be able
Hi Christopher,
On 3 Mar 2014, at 17:55, Christopher Wood wrote:
> We could have been talking in my cube. My points when I'm discussing this
> with coworkers generally go like so...
>
> If you use this:
>
> class { name: }
>
> You will only be able to declare that name once. If you declare c
(inline)
On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote:
>Hi Christopher,
>On 3 Mar 2014, at 17:55, Christopher Wood <[1]christopher_w...@pobox.com>
>wrote:
>
> We could have been talking in my cube. My points when I'm discussing
> this with coworkers generally
I'm still having these issues.
Here is some output that might help:
https://gist.github.com/anonymous/1afccb3d54ae33b48544
Any ideas?
On Tuesday, December 17, 2013 5:56:55 PM UTC+1, cko wrote:
>
> hey,
>
> so i just installed puppetdb on a dedicated server (with pgsql).
>
> I noticed that the
Hello everyone,
I am trying virtualize my users and that works out just fine, but the
problem is I have some aix users that need a particular group. So I thought
it would be a good idea to add a conditional to the virtual resource, but I
get stuck with this error:
err: Failed to apply catalog:
The group resource name is not gid but title, so change the requiere
parameter to Group[$title]
Regards
El 03/03/2014 23:33, "Race Boyer" escribió:
> Hello everyone,
>
> I am trying virtualize my users and that works out just fine, but the
> problem is I have some aix users that need a particula
(also inline)
On 3 Mar 2014, at 19:25, Christopher Wood wrote:
> (inline)
>
> On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote:
>>
>> Additionally, it creates two places in which the parameters can be
>> automatically set. eg. ntp::install::package_name and
>> ntp::params::
Support for SVN in r10k is actually brand new and is going to be released
shortly. It'll be available in 1.2.0 which is currently in RC; if all goes
well then 1.2.0 final should be released on Thursday. The CHANGELOG (
https://github.com/adrienthebo/r10k/blob/master/CHANGELOG#L11-L12) gives a
brief
Matthaus,
Here is my output from that run
cabimd011032:~ madmin$ sudo puppet agent --no-daemonize --verbose --logdest
console
Notice: Starting Puppet client version 3.4.3
Error: Could not run: Could not create PID file:
/var/lib/puppet/run/agent.pid
cabimd011032:~ madmin$
On Thursday, February
Hey all,
I notice with the munin module I wrote, the munin-node service won't start
on the first puppet run. Run it a second time, and the service starts no
problem.
The problem here I believe is that puppet is attempting to start the
service before the package is installed.
So I tried to set
On Mon, 2014-03-03 at 21:07 -0500, Tim Dunphy wrote:
>
> Error: Failed to apply catalog: Could not find dependency
> Package[munin-node] for Service[munin-node]
> at /etc/puppet/environments/production/modules/munin/manifests/service.pp:8
>
Looks to me like puppet isn't finding the declaration
Although it is not incorrect, you should not bypass class boundaries, so
it's better:
require=>Class['munin::install']
And usually you may include the diferent classes for a module in init.pp
chaining them there.
Regards,
El 04/03/2014 03:07, "Tim Dunphy" escribió:
> Hey all,
>
> I notice wit
27 matches
Mail list logo
