unable to load puppet_x/unbound/validate_addrs (on puppetserver)

Question

unable to load puppet_x/unbound/validate_addrs (on puppetserver)

Closed this issue 9 years ago · 9 comments

when running puppet-unbound under puppetserver, it seems unable to load the puppet_x module

Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
  Could not autoload puppet/parser/functions/validate_unbound_addr:
  no such file to load -- puppet_x/unbound/validate_addrs on node ns01.esat

Answer 1 · 2015-08-29T15:19:32.000Z

the appropriate puppet issue is https://tickets.puppetlabs.com/browse/PUP-4450

Answer 2 · 2015-10-12T13:17:59.000Z

I'm hitting the same issue.

Any chance this could be fixed soon?

Thanks,
Marin

Answer 3 · 2015-10-12T15:14:38.000Z

@igalic Thank you for the link and tracking.

@dnaeon This is an issue with Puppetserver as I read that ticket, so I'm not sure what we can do in this module other than to remove the PuppetX work, which I'd like not to do for rspec reasons. Feel free to comment on the ticket that igalic linked.

Answer 4 · 2015-11-23T18:55:40.000Z

Thanks xaque208, great module.

+1 is there a workaround or is this module simply not compatible with puppetserver?

Answer 5 · 2015-11-24T19:38:20.000Z

For now, its not compatible. Helping push the conversation or add more information to https://tickets.puppetlabs.com/browse/PUP-4450 may help speed this along. Also note there is a PR in on Puppet, but looking over the comments it doesn't look like puppetlabs/puppet#4445 will be merged.

Answer 6 · 2015-12-02T17:19:51.000Z

This is a long standing issue with puppet: https://projects.puppetlabs.com/issues/4248

The autoloader can load an environment specific function (or type, provider, report, etc), but the autoloader does not participate in loading its transitive dependencies. So if your function does a "raw" require puppet_x/unbound/validate_addrs, then ruby can't load it from an environment specific modulepath.

The general workaround is to require the helper code relative to the current file being autoloaded, e.g.

require File.dirname(__FILE__) + ' /../../puppet_x/unbound/validate_addrs'

I don't know if that's the right number of ..'s, but you get the idea. It's an ugly hack, but is used pretty widely in modules.

Answer 7 · 2015-12-06T00:00:19.000Z

Excellent, thank you for the information @joshcooper!

Answer 8 · 2015-12-06T00:21:24.000Z

#107

Would someone who is running Puppetserver mind testing out the above PR please?

Answer 9 · 2015-12-19T19:17:27.000Z

This should be fixed in 1.2.1.