Puppet users - Mar 2012 - Could not prefetch package provider 'freebsd': No resource and no name in property hash in freebsd instance

Hi,

I am puzzled. I installed exim-mysql on a freebsd machine without
problem before but now this manifest creates an error:

class exim::install {
  package { [ ''mail/exim-mysql'' ]:
    ensure   => installed,
    provider => freebsd,
    source   => ''http://<some_url>'',
  }
}

Here is the error:


err: Could not prefetch package provider ''freebsd'': No
resource and no
name in property hash in freebsd instance
info: Applying configuration version ''1332781404''
err: /Stage[main]/Exim::Install/Package[mail/exim-mysql]: Could not
evaluate: No resource and no name in property hash in freebsd instance
err: /Stage[main]/Puppet::Install/Package[sysutils/puppet]: Could not
evaluate: No resource and no name in property hash in freebsd instance

I had added new modules but took them all out. I am sure the package
is installed on the file server. Also, other nodes loading mysql or
apache work fine.

Any suggestions?

Thanks,

Werner Bahlke

-- 
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-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Just thought I post the solution which we eventually found.

It has to do with installing the mail/p5-Mail-SpamAssassin package and
how the new package is constructed. When we tried another test and
installed a random package (found in the ports tree) manually and ran
the agent again, we had no problem completing successfully, even
though an unknown package was installed.

The SA rule package is not "real" in the sense that it comes from the
ports tree and has an entry in the INDEX file that Puppet uses.  The
command that Puppet uses to enumerate packages is missing a piece of
information (the port''s "origin"), and that causes the error
that
we''ve seen.  Any other package installed from the ports tree has an
origin, and Puppet doesn''t have a problem, even if it didn''t
install
it.

We also found that we can prevent the sa-update cron script from
registering the package after it''s installed.  This will allow the SA
rules to be updated periodically, but it will also avoid the Puppet
error.

At the very least, we''d love to see a better error message from
Puppet, perhaps including the package name causing the failure.  That
would have tipped us off sooner.

On Mar 26, 10:07 am, wernerbahlke <werner.bah...@gmail.com>
wrote:
> Hi,
>
> I am puzzled. I installed exim-mysql on a freebsd machine without
> problem before but now this manifest creates an error:
>
> class exim::install {
>   package { [ ''mail/exim-mysql'' ]:
>     ensure   => installed,
>     provider => freebsd,
>     source   => ''http://<some_url>'',
>   }
>
> }
>
> Here is the error:
>
> err: Could not prefetch package provider ''freebsd'': No
resource and no
> name in property hash in freebsd instance
> info: Applying configuration version ''1332781404''
> err: /Stage[main]/Exim::Install/Package[mail/exim-mysql]: Could not
> evaluate: No resource and no name in property hash in freebsd instance
> err: /Stage[main]/Puppet::Install/Package[sysutils/puppet]: Could not
> evaluate: No resource and no name in property hash in freebsd instance
>
> I had added new modules but took them all out. I am sure the package
> is installed on the file server. Also, other nodes loading mysql or
> apache work fine.
>
> Any suggestions?
>
> Thanks,
>
> Werner Bahlke
-- 
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-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.