2015.2 strange message

[Vince Skahan]

Spun up a 2015.2 system and every time an agent runs we see "Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution".   Any ideas ?

I saw one bug report at https://github.com/gentoo/puppet-portage/issues/136 saying facter needed to be updated and this was allegedly done in 2015.2, but perhaps not (???)

Vagrant box I'm testing on is centos-6.7 fully patched up.

[Peter Huene]

Hi Vince,

On Thu, Aug 13, 2015 at 10:21 AM, Vince Skahan <vince...@gmail.com> wrote:

Spun up a 2015.2 system and every time an agent runs we see "Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution".   Any ideas ?

I saw one bug report at https://github.com/gentoo/puppet-portage/issues/136 saying facter needed to be updated and this was allegedly done in 2015.2, but perhaps not (???)

This was fixed in the puppet-portage module itself, so updating the module to a fixed version or porting the fix to the fact file (simply delete the require 'facter/util/resolution' line) should solve the problem with Facter 3.  This particular fix is also backwards compatible with 2.x, as 2.x also required this file before resolving any custom facts.

If memory serves, I searched through the Forge for references in custom facts depending on the Facter 2.x implementation's file structure and found only this one.  Therefore I didn't end up adding the workaround to Facter itself to support requiring parts of 2.x Facter beyond simply `require 'facter'` (which itself is also unnecessary, but was more frequently done).  We could revisit fixing this in Facter itself (basically manipulating the load path to fake the load of 'facter/util/resolution') if it proves to be a more widespread problem affecting other modules.

 

Vagrant box I'm testing on is centos-6.7 fully patched up.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--

Peter Huene

Software Engineer, Puppet Labs

Puppet Open Source Team

-------------------------------------------

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9!

[Vince Skahan]

I'm sorry but you're going to need to reparse that one into English.
You want me to check for what (where?) and change what (where?) ?

[Kylo Ginsberg]

On Thu, Aug 13, 2015 at 9:20 PM, Vince Skahan <vince...@gmail.com> wrote:

I'm sorry but you're going to need to reparse that one into English.
You want me to check for what (where?) and change what (where?) ?

The easiest fix for you would be to update to 2.3.0 or greater of the gentoo-portage module.

Kylo

 

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f1afa917-2cd3-4955-8056-5c47feba170f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kylo Ginsberg | ky...@puppetlabs.com | irc: kylo | twitter: @kylog

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.

Register now to take advantage of the Early Bird discount —save $249!

[Vince Skahan]

On Saturday, August 15, 2015 at 5:06:09 AM UTC-7, Kylo Ginsberg wrote:

On Thu, Aug 13, 2015 at 9:20 PM, Vince Skahan <vince...@gmail.com> wrote:

I'm sorry but you're going to need to reparse that one into English.
You want me to check for what (where?) and change what (where?) ?

The easiest fix for you would be to update to 2.3.0 or greater of the gentoo-portage module.

Thanks for the plain English response :-)

Seems to me that 2015.2 shouldn't have these kinds of issues.  Which PUP did you open to fix this obvious bug in the commercial product ?