Re: [Puppet Users] Raspberry pi + facter problem: Could not retrieve local facts: can't convert nil into String

[Ken Barber]

> I have installed Puppet on a Raspberry pi (running Raspbian) and it seems to
> work (sort of). I managed to add it to a Puppetmaster and sign its
> certificate but a puppet run fails:
>
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve local facts: can't convert nil into String
> Error: Failed to apply catalog: Could not retrieve local facts: can't
> convert nil into String
>
> It doesn’t show the facts that generates the error (even with the debug
> option supplied).
>
> So I executed facter on the command line (with the -p option) and got the
> following error:
>
> # facter -d -p
> Found no suitable resolves of 1 for ec2_metadata
> value for ec2_metadata is still nil
> Found no suitable resolves of 1 for lsbdistid
> value for lsbdistid is still nil
> can't convert nil into String
>
> Which made me think the lsbdistid fact was causing the problem but when I
> ran it separately it didn’t generate the error.
>
> facter -d -p lsbdistid
> Found no suitable resolves of 1 for lsbdistid
> value for lsbdistid is still nil
>
> Is there any (simple) way to find out which fact is generating the error?
>
> FYI, the following package/versions are used:
>
> ii facter 2.3.0-1puppetlabs1
> all Ruby module for collecting simple facts about a host operating
> system
> ii hiera 1.3.4-1puppetlabs1
> all A simple pluggable Hierarchical Database.
> ii puppet 3.7.3-1puppetlabs1
> all Centralized configuration management - agent startup and
> compatibility scripts
> ii puppet-common 3.7.3-1puppetlabs1
> all Centralized configuration management
> ii puppetlabs-release 1.0-11
> all "Package to install Puppet Labs gpg key and apt repo"

Its been a while since I've hacked on facter so excuse my ignorance,
but does adding --trace surface the full stack trace from that
exception?

ken.