Strange. It ended up being all my notify attributes quit working. A
restart of puppetserver solved the issue.
Kenton Brede
On Thu, Feb 2, 2017 at 3:24 PM, Kenton Brede wrote:
> As it turns out the agents.pp file is on my puppetmaster. If I comment
> out my
As it turns out the agents.pp file is on my puppetmaster. If I comment out
my 'mcollective' module then the next module in line, 'nagios' has issues:
Error: Failed to apply catalog: Could not find dependent Service[nrpe] for
File[/etc/nagios/nrpe.cfg] at
On ol7 boxes the puppet agent is working fine.
This is what I have installed on one of my ol6 boxes:
# rpm -qa |grep puppet
mcollective-puppet-common-1.11.1-1.el6.noarch
puppetlabs-release-22.0-2.noarch
puppetlabs-release-pc1-1.1.0-5.el6.noarch
mcollective-puppet-agent-1.11.1-1.el6.noarch
This thing is nice that way:
https://github.com/drwahl/puppet-git-hooks
I recommend using the pre-receive hook on the server side. That way you can
skip awkward conversations about how people should go the extra mile and exceed
expectations by installing git hooks locally. Instead you get to
Hi All,
I’m excited to announce the release of Puppet Agent 1.9.0, which includes
Puppet 4.9.0. There’s lots of good stuff in this release, but a few highlights
include:
• Hiera 5 - a successor of the experimental Puppet lookup feature - is
built into Puppet 4.9. This allows you to
On 02/02/17 14:28, Albert Shih wrote:
Hi,
We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
(last version), and every agent stop working with this error
Info: Using configured environment 'jas'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
On 02/02/17 00:46, James Boone wrote:
Is there a way to define a list of allowed values for a class parameter
so that it shows up as a drop-down menu in pe-console?
If not, would this be a feasible feature to add?
Have a common case where a parameter is a few set possible values, would
like to
Serious question:
> Puppet::SimpleResource.implement('apt_key')
What is the benefit of a construct like this compared to a regular ruby
class where it will be completely obvious to every ruby programmer how
inheritance works and what actually happens if I use a mixin?
--
You received this
Puppet 4.9.0 just went live and we are waiting for the proper release
notes to be sent out.
Early users have started to upgrade and have been running into a couple
of issues that are easily fixable.
The new implementation is sensitive to errors in hiera.yaml
I think I'm slowly talking myself into this.
The issue that I've had is that the current Data Types are composable.
There's a ticket open about it and hopefully that will fix a lot of my
issues.
Unfortunately, it looks like my heap/stack discussion was with Henrik on
Slack, so that's not super
Hello,
I found the way to do it with this module :
create a norecommend.erb file in templates folder of apt module and then
add :
apt::setting { "conf-norecommend":
content => template('apt/norecommend.erb'),
ensure => present,
}
regards,
Le jeudi 2 février 2017 09:30:32 UTC+1, Romgo a
Le 02/02/2017 à 14:28:17+0100, Albert Shih a écrit
> Hi,
>
> We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
> (last version), and every agent stop working with this error
>
>
> Info: Using configured environment 'jas'
> Info: Retrieving pluginfacts
> Info: Retrieving
On 2 February 2017 at 02:50, Trevor Vaughan wrote:
> Hi David,
>
> Most of this looks fine (I still need to digest some of it) but I don't
> know that I'm a huge fan of no munge or validate functionality. This seems
> to fly in the face of a 'fail fast' mentality.
>
With
Hi folks,
I'm grappling with a data structure that I want to model as a hash in
Puppet and ultimately mash it down to a string for use in a config file.
I'm writing out a config for Nagios BPI and there is one complex
parameter "members" which is described like this in the documentation:
#
Is there a way to define a list of allowed values for a class parameter so
that it shows up as a drop-down menu in pe-console?
If not, would this be a feasible feature to add?
Have a common case where a parameter is a few set possible values, would
like to make it easy to 'select' one.
Hello,
I can, but in this case if there is a new release for the pluggins I'll
have to change the code again.
It is better to have this option built-in.
Le jeudi 2 février 2017 09:20:09 UTC+1, R.I. Pienaar a écrit :
>
>
>
> On Thu, Feb 2, 2017, at 09:13, Romgo wrote:
> > Hello,
> >
> >
>
On Thu, Feb 2, 2017, at 09:13, Romgo wrote:
> Hello,
>
>
> I would like to use the apt module, but I can't set this preference (If I
> am not wrong) :
>
> /etc/apt.conf.d/01norecommend
> >
> > # apt : FILE MANAGED BY PUPPET
> >
> > APT::Install-Recommends "0";
> >
> > APT::Install-Suggests
Hello,
I would like to use the apt module, but I can't set this preference (If I
am not wrong) :
/etc/apt.conf.d/01norecommend
>
> # apt : FILE MANAGED BY PUPPET
>
> APT::Install-Recommends "0";
>
> APT::Install-Suggests "0";
>
Does anyone have an idea on how to implement this via this
18 matches
Mail list logo