I think this is the problem:
>platform: ubuntu-server-14.04-amd64
platform gets split into 3:
@variant, version, @arch = self.split('-', 3)
>From that you get:
["ubuntu", "server", "14.04-amd64"]
When it tries to evaluate the hash it has of platform version codes using
version ('server') it ge
On Thu, Sep 4, 2014 at 9:26 AM, jcbollinger
wrote:
>
>
> As long as you intend to perform the validation inside the fact
> implementation, the fact can keep and use its own cache somewhere on the
> system.
>
> Alternatively, the master stores the most recent set of facts provided by
> each node, a
23 PM, Felix Frank wrote:
> On 09/03/2014 06:32 PM, Khoury Brazil wrote:
> > Sorry for the delay Felix. Here's a specific example of a situation
> > where the fact might return what I would consider useless information
> > and I would want to revert back to a the value set
self) and if it doesn't meet my criteria, I can set
the fact to itself using Facter.value(console_user).
On Fri, Aug 29, 2014 at 9:04 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 08/28/2014 11:01 PM, Khoury Brazil wrote:
> > I currently have it written to reuse
I'm writing some facts for laptops and they're dependent on the
availability of specific services over the network. I'd like to use the
previous data for the fact if the data returned doesn't validate. Is there
an existing pattern I can use for that? I currently have it written to
reuse the data us
I opened a bug ticket concerning this:
PUP-2011
https://tickets.puppetlabs.com/browse/PUP-2011
--
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+unsub
For what it's worth, I was able to get it to work with "en_GB.UTF-8" in
root's shell. I was also able to get it to work by setting it to
"de_DE.UTF-8". I think puppet requires a language/locale/encoding and the
default us_ascii (on my copy of OS X) doesn't cut it.
I tried it with puppet 3.4.3 on O
That's good to hear. But I'm still concerned about Facter. Correct me if
I'm wrong, but this issue indicates that Facter 1.7.5 will be targeted but
we're currently on 1.7.4:
https://projects.puppetlabs.com/issues/22107
Did it make it into 1.7.4?
On Tue, Jan 14, 2014 at 11:05 AM, Jeff Bachtel <
On Tue, Dec 18, 2012 at 5:03 PM, Dawn Foster wrote:
>
> The Ask Q&A site just gives those people who prefer something more
> like stack overflow (with voting and other interactivity) also have a
> place where they can feel more comfortable asking questions.
>
>
> Dawn
It also incentivizes answe
on OS X with my manifests and 2.7.10.
Best,
Khoury
On Mon, Feb 20, 2012 at 1:00 PM, Matthaus Litteken
wrote:
> Khoury,
> Good point. I've updated the wiki/release notes to reflect the change.
>
> Thanks!
> -Matthaus
>
> On Mon, Feb 20, 2012 at 12:07 PM, Khoury Brazil
&
On Mon, Feb 20, 2012 at 12:07 PM, Nan Liu wrote:
> I think you've already stumbled on the answer in the previous thread.
> The cache timeout is unfortunately tied to runinterval setting. I'm
> pretty sure there's a ticket requesting to split them up. The closest
> thing you can do today:
Is there
Would it be worth updating the release notes wiki to note that the
release is no longer recommended? Generally that's where I look for
information about a particular release:
http://projects.puppetlabs.com/projects/1/wiki/Release_Notes#2.7.10
Best,
Khoury
On Sun, Feb 19, 2012 at 5:09 PM, Michael
Hi,
Starting a new thread since the question and problem are completely
different at this point. I've written modules that implement a client
side firewall and overwrite and flush any changes made by a user. This
is mandated by several different internal security policies and of
course compliance.
On Sat, Feb 18, 2012 at 12:49 PM, Khoury Brazil wrote:
> Since that's out of the way, how can I control catalog expiration on
> specific puppet agents? I'm getting these errors if a client has been
> offline for a few days:
>
> Not using expired catalog for from cac
On Wed, Feb 15, 2012 at 7:05 PM, Khoury Brazil wrote:
> I guess I *was* missing something (something very obvious...). Thanks
> for the help, that was indeed the issue. :)
Since that's out of the way, how can I control catalog expiration on
specific puppet agents? I'm getting t
On Wed, Feb 15, 2012 at 5:51 PM, Daniel Pittman wrote:
> On Wed, Feb 15, 2012 at 17:26, Khoury Brazil wrote:
>> On Thu, Feb 9, 2012 at 1:09 PM, Daniel Pittman wrote:
>>>
>>> On Thu, Feb 9, 2012 at 06:12, mukulm wrote:
>>> >
>>> > I want to c
On Thu, Feb 9, 2012 at 1:09 PM, Daniel Pittman wrote:
>
> On Thu, Feb 9, 2012 at 06:12, mukulm wrote:
> >
> > I want to cache the updates for the users system received from the
> > server so that the users can get the updates
> > from the local system cache while offline.
> >
> > Any idea how can
You could use a source code repository system. Have the client running
on the host that periodically checks in the configuration files. It
would be most useful with text configuration files but there are
repository systems like perforce that can store binaries really well.
Perforce also supports tr
No questions or problems today, just thought the list might like to
see that puppet is being used by a (another) site/company with a ton
of traffic:
http://blog.reddit.com/2012/01/january-2012-state-of-servers.html
I'm hoping I can persuade them to talk a bit more about how they use
puppet and wh
On Sun, Aug 21, 2011 at 10:15 PM, Nan Liu wrote:
>
> On Sun, Aug 21, 2011 at 7:53 PM, Khoury wrote:
> > Adding the entry "127.0.0.1 " solved the
> > problem. I suppose that means dns/reverse dns is one of the ways that
> > puppet determines what the node name is (although in my case it
> >
Hi Everyone,
I have a weird issue where the puppet client running under launchd
generates a new certificate request for 'localhost' which I thought
was pretty odd (with the side effect of it failing to run and report).
Running puppetd manually never generates this behavior.
Details:
Client:
pupp
On Mon, Jul 25, 2011 at 10:46 PM, Ohad Levy wrote:
> On Tue, Jul 26, 2011 at 5:04 AM, Khoury Brazil
> wrote:
>> On Sat, Jul 23, 2011 at 8:15 PM, Jacob Helwig wrote:
>>> On Fri, 22 Jul 2011 19:28:37 -0700, Khoury wrote:
>>>>
>>>> Hi All,
>>
not.
I'll look into the message queue. I guess a big question now is: Does
anyone know offhand if the message queue timeouts can be configured
for mcollective? My initial searches don't reveal much.
>
> On Mon, Jul 25, 2011 at 7:04 PM, Khoury Brazil
> wrote:
>>
>>
On Sat, Jul 23, 2011 at 8:15 PM, Jacob Helwig wrote:
> On Fri, 22 Jul 2011 19:28:37 -0700, Khoury wrote:
>>
>> Hi All,
>>
>> Does anyone have any experience with debian/ubuntu and or OS X with
>> regard to reporting on updates? I'm interested in getting update
>> (specifically security) states for
On Mon, Jul 25, 2011 at 10:43 AM, Alexis Midon
wrote:
> Hi Craig,
> thank you for you answer.
>
> I also tried 'has_restart => true,' before posting on this group. It
> did not fix the behavior I described: jenkins getting killed but not
> restarted.
>
> Regarding 'refresh', you seem to imply th
On Fri, Jul 22, 2011 at 10:44 PM, Nick Lewis wrote:
> On Fri, Jul 22, 2011 at 10:27 PM, Khoury Brazil
> wrote:
>> Hi All,
>>
>> Puppet-dashboard appears to be having some trouble. Under inventory, it says:
>> "Could not retrieve facts from inventory se
Hi All,
Puppet-dashboard appears to be having some trouble. Under inventory, it says:
"Could not retrieve facts from inventory service: Permission denied -
certs/dashboard.private_key.pem"
When I run:
curl -k -H "Accept: yaml" https://puppet:8140/production/facts/host.domain
I get the expected du
27 matches
Mail list logo
