t for myself where the error was.
On Jan 12, 2:11 pm, bobics wrote:
> I have the following use case, which I think is a very valid use case,
> but puppet is throwing an error. Puppet's implementation of how
> parameterized classes work with include/require breaks the
> *declarative
I have the following use case, which I think is a very valid use case,
but puppet is throwing an error. Puppet's implementation of how
parameterized classes work with include/require breaks the
*declarative* nature of Puppet. I believe this is the same bug as:
http://projects.puppetlabs.com/issu
I get around this issue by installing Puppet as a gem.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@go
Thanks for both solutions. :) Looks like either will work for me.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+un
I'd like to pass command line options for a package installed via a
gem provider. In particular, I'm updating puppet, the equivalent
command would be:
/usr/bin/gem1.8 install puppet -v=2.6.1 --no-rdoc --no-ri
(The extra docs that gets installed with puppet take WAY too long and
are unnecessa
Thanks Sandor, that worked for me.
Unfortunately I'm still seeing Puppet intermittently hang. I'll
investigate the issue some more and create a new thread if needed.
On Oct 20, 1:54 am, Sandor Szuecs wrote:
> On Oct 20, 2010, at 2:13 AM, bobics wrote:
>
> > How do I
How do I set the Ruby path that Puppet uses? I have Ruby Enterprise
Edition installed for my *application*, installed from source and
symlinked (/usr/local/bin/ruby) so it's in the path, overriding the
default .deb installed standard Ruby (/usr/bin/ruby). For *Puppet* I
want to use the standard R
See my post, probably the same issue. I had to downgrade to 0.25.5.
http://groups.google.com/group/puppet-users/browse_thread/thread/626e7334b437f4fc
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-u
Matt, thanks for the tip.
I'm using the lastest facter 1.5.7 gem, I glanced at the code and it
doesn't look like that patch applies. Should I not be using the
stable version of facter? Looks like 1.5.7 was last updated in
9/2009? :/
On Aug 2, 6:04 pm, Matt Robinson wrote:
> I was seeing simila
I downgraded to puppet 0.25.5 and it works fine now. This looks like
a bug to me, please le me know if I should file a ticket.
I spent at least an entire day on this. :(
The only weird thing I see is a Rails warning. see below:
> DEPRECATION WARNING: metaclass is deprecated and will be removed
Why is this even calling getaddrinfo in the first place? Puppet is
running totally locally. I was considering a workaround using file
paths within 'source' but it doesn't seem to like relative paths
either. :(
--
You received this message because you are subscribed to the Google Groups
"Puppet
When using file { "/tmp/bobics_fileserver": source => "puppet:///
modules/bobics/bobics_fileserver"} I get the error:
err: /Stage[main]/Bobics/File[/tmp/bobics_fileserver]: Could not
evaluate: getaddrinfo: Name or service not known Could not retrieve
file metadata for p
12 matches
Mail list logo
