-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Puppet 0.25.2 - code-named "Zoe"
This is the third release candidate for 0.25.2. The 0.25.2 release
is a significant maintenance release (123 tickets closed!) in the
0.25.x branch.
Thanks to all who contributed to the release and tested fixes -
espe
0.25.1 installed via gem on opensolaris 2009.06
I only see this error when my puppet master is set up to use mongrel
r...@puppet:~# puppetd --test
info: Retrieving plugin
err: /File[/var/puppet/lib]: Failed to generate additional resources
using 'eval_generate': No format match the given format n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael DeHaan wrote:
> Ok, some more data from git history:
> http://github.com/reductivelabs/facter/commit/33fb7709404e706801683e6c47ab7a0a5a1884b1
>
> It looks like "return an array" is new behavior for exec, and maybe it
> wasn't backported/tested
Kenneth Holter wrote:
>
> We're look into ways to implement change management to our puppet
> configurations, and this approach is very interesting as it seems very
>
Even easier: Maintain multiple Puppet infrastructures. Push your code to each
as it is ready.
Dev puppetmaster, dev puppet cli
>
> I use a workaround with an always existing empty file, like:
>
> source => [
> "puppet:///path/file.$hostname",
> "puppet:///shared/dummy_empty_file_for_workaround"
> ]
>
> This is not always suitable I guess, but I haven't found a better way.
Yeah, it won't quite work for me,
On Dec 31, 11:32 am, Michael DeHaan wrote:
> > > Though something is perhaps not kosher with it and lsb_release
> > > although it works fine for me...
>
> > The issue seems to be that Facter::Util::Resolution::exec is returning
> > an array, not a string.
> > My version of Ruby doesn't seem to w
> > Though something is perhaps not kosher with it and lsb_release
> > although it works fine for me...
>
> The issue seems to be that Facter::Util::Resolution::exec is returning
> an array, not a string.
> My version of Ruby doesn't seem to want to do pattern matches against
> arrays, it seems, t
> It's set in lsb.rb.
Thanks.
>
> Though something is perhaps not kosher with it and lsb_release
> although it works fine for me...
>
The issue seems to be that Facter::Util::Resolution::exec is returning
an array, not a string.
My version of Ruby doesn't seem to want to do pattern matches again
On Thursday 31 December 2009 15:17:56 John Vestrum wrote:
> I too am trying to implement this kind of logic. It would be very
> useful if I could do:
>
> source => [ "puppet:///path/file.$hostname", undef ]
>
> But this fails with "Parameter source failed: Could not understand
> source undef: priva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael DeHaan wrote:
> I found this post from Nov 20 regarding a bug in facter. James
> Turnbull was asking then for debug output, which I've provided a bit
> later.
>
> The real trick though is this:
>
> [mdeh...@eng-dhcp-105 facter]$ ack lsbdist
On Dec 10, 5:24 am, kapi wrote:
> Hi,
> I'm using many classes withfilereferences using multiplefile
> sources.
> Example:file{ "/path/to/my/file":
> source=> [
> "/nfs/files/file.$host",
> "/nfs/files/file.$operatingsystem",
> "/nfs/files/file.$myownhosttype,
>
I found this post from Nov 20 regarding a bug in facter. James
Turnbull was asking then for debug output, which I've provided a bit
later.
The real trick though is this:
[mdeh...@eng-dhcp-105 facter]$ ack lsbdistid *
lib/facter/operatingsystem.rb
11:if Facter.value(:lsbdistid) == "Ubunt
We're look into ways to implement change management to our puppet
configurations, and this approach is very interesting as it seems very
straight forward and easy to maintain (btw, it's very similar to the
approach described on http://fnord.no/sysadmin/puppet/staging). As described
on that web site
13 matches
Mail list logo
