Issue #13501 has been updated by Chris Price.

Status changed from Unreviewed to Needs More Information
Assignee set to Werner Bahlke

As the problem is described, I fully agree that we should at least provide a 
better error message.  Can you possibly provide a bit more info to help us out 
with this?

1. OS version#
2. puppet version
3. a bare minimum manifest that tries to install the problematic package, and 
ideally can be used to reproduce the error via a simple "puppet apply"
4. output of apply/agent run with "--trace" flag

Any or all of the above will be very useful to us.
----------------------------------------
Feature #13501: Better error message for err: Could not prefetch package 
provider 'freebsd': No resource and no name in property hash in freebsd instance
https://projects.puppetlabs.com/issues/13501#change-58903

Author: Werner Bahlke
Status: Needs More Information
Priority: Normal
Assignee: Werner Bahlke
Category: 
Target version: 
Affected Puppet version: 
Keywords: error message, freebsd provider
Branch: 


This error 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.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

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

Reply via email to