On 19/06/13 07:17, cko wrote:
hi,
I'm trying to run the following manifest on my puppet agent: (snippet)
package { 'check_mk-agent-logwatch-1.2.3i1-1.noarch':
provider => 'rpm',
ensure => installed,
source => 'http : //
mathias-kettner.de/download/check_mk-agent
hi,
I'm trying to run the following manifest on my puppet agent: (snippet)
package { 'check_mk-agent-logwatch-1.2.3i1-1.noarch':
provider => 'rpm',
ensure => installed,
source => 'http : //
mathias-kettner.de/download/check_mk-agent-logwatch-1.2.3i1-1.noarch.rpm',
Is there any way to pass puppet run details to an ENC. Most importantly I
want to know the Environment value the puppet Agent is asking for. More
generally is it possible to query the puppet configuration values?
One thought I had is to turn the puppet config into FACTS. Then the ENC can
get t
> > You might find it convenient and logical to structure it as one
> > large, complex, nested value, from which the individual
> > components would select the pieces they need. For example, a
> > hash with VM hostnames as keys, and hashes of VM names to VM
> > parameter hashes as values (i.e. a t
I'm having some trouble getting a silent install of Firefox to run with the
windows package provider. My manifest looks like this:
package { "Firefox Setup 21.0":
ensure => installed,
source => 'C:\\Files\\Firefox Setup 21.0.exe',
install_options => ['/S']
}
When this is executed by 'pupp
On 13-06-17 04:04 AM, Rajat Patel wrote:
Hi Guys,
We have Cent OS 6.4 server which is puppet master server, its take all
mix environment(fedora/redhat/centos/windows).
Right now we have add 2 node one from ubuntu 12.10 and fedora 18.
If the dashboard is using ruby 1.8.x, it cannot process rep
Hi.
First off my situation is this;
I have a module that's split up in such a way that it runs as follows:
Install packages => Ensure files are present => insure service is running.
Now say I have a stable cluster up and running. I want to push a new file
change on a configuration to all slave
Hello guys, I am facing a problem with puppet client installed via gem due
Ruby EE.
The problem is the following:
> puppetd -vt
info: Caching catalog for #FQDN
err: Could not run Puppet configuration client: Could not find a default
provider for augeas
I have tried to install ruby-augeas(gem inst
To diagnose this you'll want to get a full stack trace. Since the error is
on the master you run the master with --trace and then find the stack trace
in the log.
On Tue, Jun 18, 2013 at 11:08 AM, Greg Chavez wrote:
> I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to
> puppet-
FYI, my bad! I had centos base repo disabled my first try. It is working
now. :P
===
I tried using yum repo from puppetlab to install puppet client on centos5,
it seems missing dependency virt-what and libselinux-ruby
On Tuesday, June 18, 2013 10:09:59 AM UTC-7, Matthaus Litteken wrote:
>
> Dear
I know this post is 1 year old, but I was having a problem just like this
and this was the first result on google. I'm just posting my experience in
hopes that it might help someone else.
I am using puppet enterprise 2.8.1 and installing the agents on a mix of
Ubuntu 10.04 & 12.04 machines. The
Some personal notes among the lines...
On Tuesday, June 18, 2013 6:35:18 PM UTC+2, Ken Barber wrote:
>
> > Although I agree that to be reusable, modules need to provide certain
> types
> > of levers, knobs, and switches, as appropriate for their scopes, I think
> the
> > case is weak for those
Awesome!
I tried using yum repo from puppetlab to install puppet client on centos5,
it seems missing dependency virt-what and libselinux-ruby, can probably
find those somewhere else but it would be nice if it is included in
puppetlabs dependencies.
Thanks!
On Tuesday, June 18, 2013 10:07:50
I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to
puppet-3.2.1-1.el5. Ruby sits at ruby-1.8.7.370-1.el5. I ran some
tests and everything seemed good so I pushed it out.
Since then, all my puppet clients are failing with this:
Error: Could not retrieve catalog from remote serve
Dear Puppet Enterprise Users,
Puppet Enterprise 2.8.2 is now available.
This is a security release of Puppet Enterprise. All users of Puppet
Enterprise are strongly encouraged to upgrade when possible to Puppet
Enterprise 2.8.2.
Puppet Enterprise 2.8.2 includes fixes to address CVE-2013-3567.
F
Puppet 3.2.2 is now available. 3.2.2 addresses a security
vulnerability discovered in the 3.x series of Puppet. This
vulnerability has been assigned Mitre CVE number CVE-2013-3567.
All users of Puppet 3.2.1 and earlier are strongly encouraged to
upgrade to 3.2.2.
For more information on this vuln
Puppet 2.7.22 is now available. 2.7.22 addresses a security
vulnerability discovered in the 2.7.x series of Puppet. This
vulnerability has been assigned Mitre CVE number CVE-2013-3567.
All users of Puppet 2.7.21 and earlier who cannot upgrade to the
current version of Puppet, 3.2.2, are strongly e
> Although I agree that to be reusable, modules need to provide certain types
> of levers, knobs, and switches, as appropriate for their scopes, I think the
> case is weak for those controls needing to be called by the same names. At
> best, naming conventions for such things might improve ease of
On Monday, June 17, 2013 9:32:36 AM UTC-5, Alessandro Franceschi wrote:
>
> Puppet is a language and so people do the same things in different ways,
> and they all work and do what they are supposed to do.
> But if we think about modules REUSABILITY and INTEROPERABILITY some
> patterns have to
Great, that makes sense, thanks!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to
Hi,
I'm trying to figure out what is the best way to handle a single system
> that dual boots with a puppet client running in each. In this case we are
> talking about Ubuntu 12.04 and Windows 8. Should I just copy the
> certificate from one OS to the other? Should I have a different
> cert
I'm trying to manage a cisco switch for testing purposes.
When I'm running: puppet device verbose I get the following error
Notice: Did not receive certificate
When I'm trying to sign the device I receive:
[root@pup-t01 etc]# puppet cert sign sw1
Error: Could not find certificate request for sw1
Hi,
I'm currently receiving the above error trying to start the puppet master.
I've followed the instructions to install PuppetDB and puppetdb-terminus,
through packages, but I cannot get it to start up.
The master would run successfully before setting up PuppetDB.
The host system is running C
I've actually just raised an issue for the problem I just posted, I found
the solution. Please see:
http://projects.puppetlabs.com/issues/21283
Alastair
On Wednesday, 24 October 2012 21:58:19 UTC+1, Deepak Giridharagopal wrote:
>
> We ended up hashing this out on the #puppet IRC channel earlier
Hi Chris,
I think I've narrowed the issue down.
I'm able to use the 10.2.0.2 f5 gem in a simple script with F5 v11.3.0 to
create an f5_node so it looks like the F5 is keeping some
backwards-compatibility.
The problem is only occurring when the F5 gem is used within puppet. The f5
gem is using
On Tuesday, June 18, 2013 11:16:15 AM UTC+2, Matthias Saou wrote:
>
> On Mon, 17 Jun 2013 07:32:36 -0700 (PDT)
> Alessandro Franceschi > wrote:
>
> > Thanks for your opinion, even if I don't fully agree with it.
> > Puppet is a language and so people do the same things in different
> > ways,
Fixed. Was an issue of rubygems. Solved by downloading from external repo:
As I don't want to activate my RHN subscription, I downloaded it from
CentOS free rpm online repository, that was suitable for my version (RHEL
6.4 - 64bit) at:
*
http://rpm.pbone.net/index.php3/stat/4/idpl/20348086/dir
On Mon, 17 Jun 2013 07:32:36 -0700 (PDT)
Alessandro Franceschi wrote:
> Thanks for your opinion, even if I don't fully agree with it.
> Puppet is a language and so people do the same things in different
> ways, and they all work and do what they are supposed to do.
> But if we think about modules
Hi,
Back with some Sweet god news :) and found the missing part. As
mention I tried to install on RHEL 6.4 testing server and failed on
rubygems.
Few days ago I had a remote session with one of my valuable friends that
guess what, also had this issue and it's all was around rubygem
i
29 matches
Mail list logo
