On Wed, Nov 30, 2011 at 5:12 PM, Ken Barber wrote:
> Hi Carles,
>
> You probably want the foreman-users mailing list for foreman related
> questions, so I'm cross-posting for you.
>
> As part of the ENC script, facts can be pushed up to foreman whenever
> a node does a 'puppet run'. There are prob
Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was
being previewed in the 2.7.7rc series as well as some new content.
Key highlight in this release (beyond items from 2.7.7rc series) are:
* Allow providers to be selected in the run they become suitable
* Showdiff is now not
Facter 1.6.4rc1 is a maintenance release candidate containing fixes, updates and
refactoring. It resolves issues #10885, #11041, #10490, and #10444. Full
release notes below.
Please note that #11041 changes the dependencies for building or
installing Facter on linux systems.
Without dmidecode, c
On Wed, Nov 30, 2011 at 7:41 PM, Dave Alden wrote:
> Hi,
> Is there some way to have an exec run only if you pass a tag on the command
> line? For example:
>
>
> class fubar {
> exec { 'reboot-system':
> refreshonly => true,
> command => '/usr/bin/reboot',
> subscribe => Class["dummy"
Hi,
Is there some way to have an exec run only if you pass a tag on the command
line? For example:
class fubar {
exec { 'reboot-system':
refreshonly => true,
command => '/usr/bin/reboot',
subscribe => Class["dummy"]
}
}
As I would expect, this throws an error the it can't f
Hi Den,
I actually thought about file resource as well but didn't able to work
out how to manage that as there could/should be more than one line to
change and I that would be need to do basis.
Cheers,
San
On Nov 30, 8:39 pm, Denmat wrote:
> Hi,
>
> I can't help directly with your issue cause
On Tue, Nov 29, 2011 at 8:06 PM, Brian Warsing wrote:
> Hi,
>
> I built a primitive type/provider for computergroups on Mac OS X. To
> implement the standard provider#exists? method, I tried to grab a
> plist from dscl and compare it with the resource definition. I didn't
> get very far...
>
> err
Hi,
I can't help directly with your issue cause I'm not at a computer but wouldn't
it be easier to use a file resource with a template in this case rather than
mess around with the escaping in the execs?
Cheers,
Den
On 01/12/2011, at 6:33, Sans wrote:
> Hi there,
>
> I'm basically trying t
Hi there,
I'm basically trying to change a line this:
myenv_set "MY_SW_DIR_1" "/exp/dir/sw1"
to
myenv_set "MY_SW_DIR_1" "/exp/fs/sw1.ac.uk"
in the one of the "/etc/profile.d/" file. So, I've defined it like
this:
-
define env_check($file, $string, $swdir, $refreshonly
On Tue, Nov 29, 2011 at 06:05:20PM +, Russell Howe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 29/11/11 14:06, jasper.hargrea...@m-w.co.uk wrote:
> > Hi all,
> >
> > Recently upgraded one of our puppet servers from 2.6.4 to 2.7.5, and
>
>
> >
> > "pu
On Wed, Nov 30, 2011 at 8:40 AM, Josh Cooper wrote:
> On Wed, Nov 30, 2011 at 6:48 AM, Felix Frank
> wrote:
>>
>> Hi,
>>
>> On 11/01/2011 02:42 PM, Luke Bigum wrote:
>> > It also has to do with Puppet's implementation of File resources: it
>> > creates in memory Ruby objects for every file and di
Agreed.
On Wed, Nov 30, 2011 at 5:31 PM, Mohamed Lrhazi wrote:
> Right. hostnames are attractive ideal use case:
>
> - Allow all from nagios.my.dom.ain
>
> If someone changes the IP address of the monitor server, puppet would
> find out and fix the rule on all the monitored nodes!
>
> Maybe s
Right. hostnames are attractive ideal use case:
- Allow all from nagios.my.dom.ain
If someone changes the IP address of the monitor server, puppet would
find out and fix the rule on all the monitored nodes!
Maybe such a simplistic and ideal case is rare in the real world, but
it is attractiv
On Wed, Nov 30, 2011 at 12:00 PM, Felix Frank
wrote:
> On 11/14/2011 09:12 PM, tmpup wrote:
>> So, basically, I need a way to specify optional parameters with
>> defines(). I'll keep looking around, but if anyone has any quick
>> tips, it would be appreciated.
>
> Hi,
>
> on the risk of repeating
On 11/14/2011 09:12 PM, tmpup wrote:
> So, basically, I need a way to specify optional parameters with
> defines(). I'll keep looking around, but if anyone has any quick
> tips, it would be appreciated.
Hi,
on the risk of repeating myself ;)
define my_file($ensure="present",$owner="",$mode="",c
Hi,
On 11/10/2011 07:59 PM, Rafael Tomelin wrote:
> Puppet-agent03.domain + (C0: 20:0 C: CA: 0D: CE: 0B: B0:
> FF: 71:51:73:5 B: 16: B6:00)
puppetca - sign-puppet agent03.domain
> err: Could not call sign: Could not
> find certificate request for puppet-agent03.domain
your puppetca line looks h
On Wed, Nov 30, 2011 at 6:48 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> Hi,
>
> On 11/01/2011 02:42 PM, Luke Bigum wrote:
> > It also has to do with Puppet's implementation of File resources: it
> > creates in memory Ruby objects for every file and directory it finds
> > recursive
Hi,
On RHEL6, no matter which version of puppet installed, I can not start
the puppetmaster service:
service puppetmaster restart
Stopping puppetmaster: [FAILED]
Starting puppetmaster: /usr/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:36:in `gem_original_r
Yeah - I'm glad you spotted that I was just about to point it out.
Its a hairy problem - Jonathan has submitted a patch for it but its
stil in review. Generally the feeling is that having iptables use
hostnames can be flakey at times - especially if you try to add a rule
for a host where DNS is mi
> Thank a lot Ken... Just to be sure and clear, the "lockout" problem is
> not about locking puppet agent itself out, that is :
>
> - All the rules, part of the catalogue, are retrieved from the puppet
> master in one go, then applied one after another, in unpredictable
> order, but there is no cha
Just saw this bug report: http://projects.puppetlabs.com/issues/10723
Sorry. Thanks.
On Tue, Nov 29, 2011 at 8:50 PM, Mohamed Lrhazi wrote:
> Hello,
>
> The source and destination parameters accept both IP address or a
> hostname. If using a hostname, the firewall module thinks the rule
> change
Thank a lot Ken... Just to be sure and clear, the "lockout" problem is
not about locking puppet agent itself out, that is :
- All the rules, part of the catalogue, are retrieved from the puppet
master in one go, then applied one after another, in unpredictable
order, but there is no chance of fire
Ok, I've resolved this. The reason puppet wasn't able to make the database
connections, any database for that matter, was the rubygem-activerecord
package wasn't installed. I figured this out by switching back to
puppetmasterd and running with "--debug --no-daemonize --verbose" and
seeing the messa
Hi Carles,
You probably want the foreman-users mailing list for foreman related
questions, so I'm cross-posting for you.
As part of the ENC script, facts can be pushed up to foreman whenever
a node does a 'puppet run'. There are probably other pre-built
mechanisms for doing this however specific
Just to avoid misunderstandings: You wrote: "but it's failing to create the
database". Be sure that *you* have created the database before! Puppet will do
the initial setup of the tables but it expects to have the database in place.
So you need to do something like that:
01[root@bob ~]# m
On 11/30/2011 03:41 PM, Felix Frank wrote:
> I'm unfamiliar with the ec2 fact. Is it one of your own?
Just saw the other thread. Never mind.
--
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@googl
Hi,
On 11/01/2011 02:42 PM, Luke Bigum wrote:
> It also has to do with Puppet's implementation of File resources: it
> creates in memory Ruby objects for every file and directory it finds
> recursively, so combine that with the md5 summing and you'll blow out
> your CPU and memory usage very quick
Hi,
On 11/07/2011 06:36 PM, Peter Horvath wrote:
> Hi,
>
> I've got a new install of Ubuntu lucid lynx with backport puppet
> 2.6.1, but when i try to run my templates i get this error.
>
> /usr/lib/ruby/1.8/timeout.rb:60:in `open': execution expired (Timeout::Error)
> from /usr/lib/ruby
On Nov 29, 3:01 pm, beamin melbin wrote:
> I have a define that looks like this:
>
> define user::sys_user($fullname, $uid, $groups, $shell='/bin/bash',
> $authkey, $authkey_type=rsa) {
> $username = "sys_${name}"
> group { $username:
> gid => $uid,
> }
>
Installing the new version of Foreman in our current Puppet
environment and I don't really want to share the same database as we
rely so much in exported resources.
As I've read in
http://theforeman.org/projects/foreman/wiki/Puppet_Facts it's possible
to push the Puppet facts using the "push_fact
The rule order is lexical based on comment, however the order which
they get applied to the running ruleset during a puppet run, without
proper puppet ordering can be effectively random. This follows the
same rules as any puppet resource without explicit/implicit ordering.
Because of this, you may
On Nov 29, 4:00 pm, Namrata wrote:
> Thanks everyone for the clarifications to a puppet newbie aka me :)
> It is much clear now.
>
> It is just that one of my puppet client is a cloud server on Rackspace
> and while it can connect to the puppetmaster and apply basic
> configurations(like write a
Hi Bernd,
I've tried with and without dbsocket being set but it has no affect.
--
Later,
Darin
On Wed, Nov 30, 2011 at 3:53 AM, Bernd Adamowicz <
bernd.adamow...@esailors.de> wrote:
> Did you try uncommenting the ‘dbsocket’ line? Maybe you should check where
> the ‘mysql.sock’ file is actually
Did you try uncommenting the 'dbsocket' line? Maybe you should check where the
'mysql.sock' file is actually located - it might not be default. For me this
works pretty good:
[master]
user = puppet
group = puppet
reports = puppet_dashboard
34 matches
Mail list logo
