Here's a summary of issues that have been fixed in puppet since our
last email. More information about each issue can be found at:
http://projects.puppetlabs.com/issues/
In Puppet 2.7.x and later
(#3757) - Brice Figureau provided support for disabling a daemonized
puppet agent as soon as it co
This is actually in Facter.
Can you bug report here please?
http://projects.puppetlabs.com/projects/facter/issues
If you can give us a cheap way to detect if infiniband is in use, we can
fix this.
On Mon, Jan 2, 2012 at 2:24 AM, ew wrote:
> Hi all,
> we maintain our cluster (SL 6.0 X86-64) wi
You must be getting the real hostname from somewhere programmatically. I
would either override $hostname and $fqdn or create a $realname custom fact
using that info. The override might be cleaner, otherwise you may want to
use either run stages or a deployment-specific environment to make sure the
Check your kernel and compare against this bug:
https://projects.puppetlabs.com/issues/10418
It sounds to me like your puppet client is hung, which is why the kick isn't
working. So the problem isn't the kick, it's the client state.
On Jan 2, 2012, at 7:51 AM, Pavel Weber wrote:
> I have exact
Hi all,
In the process of converting a largish installation (around 150 hosts,
mixed cloud and physical) to Puppet and I have a question about how
folks manage hostnames.
The TL; DR version:
On first run, I can't use $hostname from facter as it's 'wrong'; for
things like doing host { $certname:
Hi all,
I've created a script to glue together several parts of Puppet
Enterprise 2.0.
It enables me to deploy a server by simply creating a DNS record and
starting this script.
This script:
- Clones a VMWare template
- Configures the network
- Installs the Puppet-client on the new mach
On Mon, Jan 2, 2012 at 5:24 AM, ew wrote:
> Any ideas on that ?
Looks like puppet is internally using ifconfig, which is deprecated,
and some ioctl that it's doing isn't liked by the IB driver. Just a
warning and nothing to be particularly concerned about (unless you're
using puppet to configure
Hi Mario,
I have exactly the same problem you described. Have you got the solution
for this? I didn't find any reply for your question. What we found that
there is the puppetdlock file in directory: /var/lib/puppet/state on
the host. If the file is there then it shows the message while runn
> Try using ruby 1.8.7 patchlevel 334, I've seen similar problems with later
> versions.
Yes, that solves the problem. Thanks.
I'm surprised that even differences in the ruby patch level matter.
I'd read
the puppet windows wiki, which mentions ruby 1.8.7 p334, but had
assumed that
meant version 1
Hi all,
we maintain our cluster (SL 6.0 X86-64) with puppet (client / master
2.7.1). The cluster is equipped with infiniband hardware.
Although everything works fine we have some strange messages on each
system during a puppet run:
puppet agent -t --noop
notice: Ignoring --listen on onetime run
in
10 matches
Mail list logo
