standalone puppet file source error "Could not evaluate: getaddrinfo: ..."

[bobics]

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 puppet:///modules/bobics/bobics_fileserver:
getaddrinfo: Name or service not known at /home/debian/puppet_sample/
modules/bobics/manifests/init.pp:8

Any idea why I might be getting this error? I can provide my sample
project if needed (you should be able to reconstruct it with the info
below).

I'm using Puppet 2.6 on a Debian virtual machine. Standalone puppet
is launched with the following command:
sudo puppet -v manifests/site.pp --confdir=.

### site.pp ###
node default {
include bobics
}
###

### init.pp ###
class bobics {
file { "/tmp/bobics_installed":
ensure => present
}

file { "/tmp/bobics_fileserver":
source => "puppet:///modules/bobics/bobics_fileserver"
}
}
###

### puppet.conf ###
[puppet]
###

I have a very simple puppet structure:
manifests/
site.pp
modules/
bobics/
files/
bobics_fileserver (just a text file)
bobics_installed (just a text file)
manifests/
init.pp
puppet.conf

Thanks,
-Andy

[bobics]

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. :(

[bobics]

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 from Rails 2.3 (use singleton_class instead). (called from meta_eval at /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/puppet-0.25.5/lib/puppet/util/metaid.rb:4)

[Matt Robinson]

I was seeing similar problems and it had to do with a bug in facter
since it wasn't confining a windows fact to windows. Try this patch
on your facter:

http://github.com/nicklewis/facter/commit/b2c21145885c15abc43b3641fcf903e13a859565

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>

[Peter Meier]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/03/2010 03:28 AM, bobics wrote:
> 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.

if you don't find another bugreport, that describes that problem, you
should file one.

cheers pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxXg4EACgkQbwltcAfKi39odwCfTCB9TMpD6u+fmRotuKypoi4n
KvkAoLEvd2tDIi7BAEW84BaSobXMU3vI
=DQPF
-----END PGP SIGNATURE-----

[bobics]

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 <m...@puppetlabs.com> wrote:
> I was seeing similar problems and it had to do with a bug in facter
> since it wasn't confining a windows fact to windows.  Try this patch
> on your facter:
>

> http://github.com/nicklewis/facter/commit/b2c21145885c15abc43b3641fcf...

[Matt Robinson]

If downgrading to 0.25 fixed this, then the problem probably isn't
with facter, and as you say, older versions of facter wouldn't have
the bug I mentioned. The patch I suggested would only have fixed
things if you were running facter from source.

So yes, please file a bug report with the info necessary to reproduce
this, which it looks like might all be already in your email.
Matt