Hi,
We are having a Puppet meetup in Seattle on Wednesday the 14th at 6:30.
Andy picked out a new spot, Radiator Whiskey, which looks awesome. Hope
to see you there.
http://www.meetup.com/Seattle-Puppet-Meetup/
-g
--
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +
Hi,
Previously i have used puppetdasboard as ENC. I have created many groups
in puppetdashboard.
Now i installed and configured Foreman as ENC. Now i would like to import
existing pupportdashboard grouping in foreman.
Is it possible?
Regards,
Suresh
--
You received this message because
Hi Henrik,
On Saturday, May 10, 2014 2:56:19 PM UTC-4, Henrik Lindberg wrote:
In 3.5 the new evaluator was added and it is on by default when using
> --parser future. If you want to turn it off you can use --evaluator
> current in addition to --parser future)
>
> If it works under --evaluator
On 05/12/2014 03:16 PM, Christopher Wood wrote:
I get the same behaviour in 3.4.3, however:
"The noop setting allows you to globally enable or disable noop mode, but it will
not override the noop metaparameter on individual resources."
http://docs.puppetlabs.com/references/latest/metaparameter
Hello John,
I made a mistake in writing , i am using exec resource to execute that
script.
Regards,
Ritesh
On Mon, May 12, 2014 at 7:05 AM, jcbollinger wrote:
>
>
> On Saturday, May 10, 2014 7:49:18 PM UTC-5, Ritesh Nanda wrote:
>>
>> Hello John,
>>
>> Thanks for your reply , ruby code i was t
That looks like a puppet bug of the exec rype. see e.g.
http://stackoverflow.com/a/14381862/4918 for how this message can be
triggered.
Another possibility might be that the machine in question is running out
of resources or is being shutdown while the agent is running?
Regards, David
On 2
Is there an issue with using subscribe? So in my virtual resource
definition I have:
define accounts::virtual ($uid,$realname,$pass) {
user { $title:
ensure=> 'present',
uid => $uid,
gid => $title,
shell => '/bin/bash',
That's great to hear; thank you for testing that Antoine!
- Josh
On Mon, May 12, 2014 at 3:24 AM, Antoine Cotten wrote:
> Hi Josh, hi all,
>
> So, I have set the environment_timeout setting to a couple of test
> values, including 30s, 1h and unlimited:
>
>- *30s* - No performance boost. Too
I doubt the problem I was referring to would have any impact on
CentOS. The problem was that we were building on SPARC, and had used
compile options that caused the build to go to a "lowest common
denominator" architecture of SPARC V7, which does not have a lot of
important SPARC V9 assembly instr
Any chance you can share what configuration options were non-optimal?
We're having some timeout issues as well on CentOS.
On Thursday, 5 September 2013 14:32:56 UTC-4, Pete Hartman wrote:
>
> Being able to set the timeout long enough gave us enough data to find the
> problem.
>
> Our SPARC build
Occasionally one of my osx servers will fail a puppet run. If I run it
again manually it works fine. It happens about once per day. Puppet agent
runs every hour. Any Ideas what this means? All I'm doing is writing a
string value to a plist file.
Here's what the puppet log says in Dashboard.
On Monday, May 12, 2014 3:55:57 AM UTC-5, Jonathan Gazeley wrote:
>
>
> This crossed my mind. NFS-mounted lock files seem like a disaster waiting
> to happen, though. I suppose the puppetmaster could host the NFS share and
> then if the puppetmaster or the network is down, the node wouldn't hav
On Monday, May 12, 2014 3:55:57 AM UTC-5, Jonathan Gazeley wrote:
>
> On 09/05/14 20:33, jcbollinger wrote:
>
>
>
> On Thursday, May 8, 2014 8:58:52 AM UTC-5, Dirk Heinrichs wrote:
>>
>> Am 08.05.2014 15:34, schrieb Jonathan Gazeley:
>>
>> I suppose it would be possible to disable the agent
I have updated "chocolateyinstall.ps1" in my chocolatey package to perform
some steps at the time of installation.
It works fine when I run it on a 64 bit command prompt. But, when i run it
from puppet its not working.
I'm pretty sure its got to do with the puppet agent running on 32 bit. The
m
I get the same behaviour in 3.4.3, however:
"The noop setting allows you to globally enable or disable noop mode, but it
will not override the noop metaparameter on individual resources."
http://docs.puppetlabs.com/references/latest/metaparameter.html#noop
No-op being false means that yes-op is
On Saturday, May 10, 2014 7:49:18 PM UTC-5, Ritesh Nanda wrote:
>
> Hello John,
>
> Thanks for your reply , ruby code i was trying to run was on client , so i
> am doing with inline_template right now , yeah but your idea seems good to
> have a plugin to do it .
>
A plugin or an Exec is the *
Hi,
I had an issue with my --noop run actually overwriting files on machine
it is run on.
After looking into it, I found that some of my modules have 'noop' param
on resources. For example:
class something ( $noops => false ) {
file { '/etc/something':
noop => $noops,
}
}
After
Hi Josh, hi all,
So, I have set the environment_timeout setting to a couple of test values,
including 30s, 1h and unlimited:
- *30s* - No performance boost. Too short for me, my Puppet runs are
distributed every 37s
- *1h* - Very good results, fast config retrieval, even slighly better
On 09/05/14 20:33, jcbollinger wrote:
On Thursday, May 8, 2014 8:58:52 AM UTC-5, Dirk Heinrichs wrote:
Am 08.05.2014 15:34, schrieb Jonathan Gazeley:
I suppose it would be possible to disable the agent from running
as a daemon and use cron, and the cron job could easily use a
19 matches
Mail list logo
