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
for reporting
purposes. Depending on transient states like that for actual application of
configuration seems fragile at best.
--
Khoury
>
> John
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
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
en to
reuse the data using Facter.value() after validation but wanted to make
sure there wasn't something standardized that I missed.
Thanks,
Khoury
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
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
privatekeydir: Permission
denied - /etc/puppet/ssl/private_keys/10-7mac.home.pem
Setting the LANG environment variable fixes that issue as well and puppet
writes the key as expected.
On Wed, Mar 19, 2014 at 4:43 AM, Merlin Hartley
wrote:
> perfect!
> Thanks Khoury!
>
> Here is m
ugh (bug?).
On Tuesday, March 18, 2014 6:36:56 PM UTC-7, Khoury wrote:
>
> I'm seeing the same behavior with the plist on 10.9.2: Puppet runs fine
> using the CLI but doesn't work as a LaunchDaemon. Did you manage to work
> out why this happens?
>
--
You received this m
I'm seeing the same behavior with the plist on 10.9.2: Puppet runs fine
using the CLI but doesn't work as a LaunchDaemon. Did you manage to work
out why this happens?
On a fresh OS X 10.9 install I didn't have any issues but 10.9.2 may have
broken something. I get the same behavior with Puppet
k.
>
> Jeff
>
>
> On 01/14/2014 01:15 PM, Khoury wrote:
>
> Does anyone know what the status is on Mavericks support? Has anyone
> tested it? It's been a while since the public release and Apple's policy of
> forcing new Macs to use Mavericks puts is in a tight s
Does anyone know what the status is on Mavericks support? Has anyone tested
it? It's been a while since the public release and Apple's policy of
forcing new Macs to use Mavericks puts is in a tight spot if we can't get
Puppet support for the OS.
Thanks,
Khoury
On Friday, Nov
ine asking them on a site like ask.puppetlabs.com.
---
Khoury
--
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet
;
>
> On Sunday, September 30, 2012 11:40:42 PM UTC-5, drew khoury wrote:
>>
>> May have spoken too soon.
>>
>> If I set the env variable, and I'm manually logged, then I run puppet all
>> is good.
>>
>> I'm still not clear on how I set
anding how Vagrant is invoking Puppet.
On Monday, October 1, 2012 12:30:35 PM UTC+10, drew khoury wrote:
>
> Looks like I was able to get it to work by executing the export command
> through a bash script, initiated via puppets exec logic in my puppet
> manifest. Not the most elegant
+10, drew khoury wrote:
>
> Setting the env variable manually does work, however I'm trying to run
> puppet via Vagrant, so I wonder where I have to set the http_proxy variable
> to get it to work when puppet is loaded via Vagrant.
>
>
> On Monday, October 1, 2012 11:03
ep 30, 2012 at 5:36 PM, drew khoury
> > wrote:
>
>> Also I tried upgrading puppet and got the same results.
>>
>> vagrant@vagrant-debian-squeeze:/tmp/vagrant-puppet/manifests$ sudo
>> apt-show-versions | grep puppet
>> facter/squeeze uptodate 1.6.12-1puppetla
puppetlabs-release/squeeze uptodate 1.0-5
On Monday, October 1, 2012 10:18:25 AM UTC+10, drew khoury wrote:
>
> Hi,
>
> I've been trying to pass the http_proxy_host option to puppet but it's not
> taking.
>
> I have tried the following:
> sudo puppet apply -
Hi,
I've been trying to pass the http_proxy_host option to puppet but it's not
taking.
I have tried the following:
sudo puppet apply --debug --verbose --http_proxy_host
http://user:p...@fqdn.com.au --modulepath '/tmp/vagrant-puppet/modules-0'
/tmp/vagrant-puppet/manifests/default.pp
sudo puppe
of course, such a simple typo, thanks so much! Too many years of typing
.php, will have to get my mind in the puppet world now :)
On Monday, September 24, 2012 9:50:41 AM UTC+10, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "drew kh
I posted a vagrant/puppet
issue
https://groups.google.com/forum/?fromgroups=#!topic/vagrant-up/36lz6yKGfDw
(still not sure where the issue lies) so I thought I'd try my luck on the
puppet group too.
I am trying to load the most basic example of a module as per the puppet
docs, using a default
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
&
/2012, expires on 03/08/2012 and the client is back on the
network with the puppet master again on 02/26/2012 does the client
pull a new catalog that would then expire on 03/11/2012?
Thanks,
Khoury
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&
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:
ably using puppet with servers and perhaps 'mostly-online' client
workstations. Even when dealing with laptops, I imagine for most
there's not frequently a concern about a consistent and frequent
applications of a catalog to conform with security policies.
Thanks for any insight you may h
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
t and what kinds of problems it helps them solve.
-Khoury
--
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet
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 no
On Aug 21, 5:30 pm, Khoury Brazil wrote:
> 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).
&
hanks for any insight you may have. This one has me kind of stumped.
Thanks,
Khoury
--
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@googlegroups.com.
To unsubscribe fro
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 up
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
erver: 'puppet'
# Port for the inventory server.
inventory_port: 8140
Any ideas? I'm stumped at this point. It almost seems like the
dashboard isn't asking for inventory at all. I've restarted all
services with no change, on both the master and dashboard hosts.
Thanks,
Khoury
-
to avoid going the centos/redhat route for my servers. I'm
thinking of using unattended-upgrade --debug --dry-run on Debian/
Ubuntu and maybe softwareupdate on OS X to build custom facts.
Thanks in advance.
Best,
Khoury
--
You received this message because you are subscribed to the Go
40 matches
Mail list logo
