Could not autoload puppet/parser/functions/artifactory_sha1: no such file to load -- puppet_x/bodeco/util #320
Comments
|
I am impacted by this as well, puppet 6.9.0 Applying mentioned patch (#329) manually fixes the problem. |
|
In puppet-archive 4.4.0 problem still exists. Could you please merge above patch ? |
alexjfisher
added a commit
to alexjfisher/puppet-archive
that referenced
this issue
Dec 6, 2019
This doesn't seem to have been neccessary for all users and probably depends on how puppetserver has `ruby-load-path` configured. See https://tickets.puppetlabs.com/browse/SERVER-973?focusedCommentId=224547&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-224547 Requiring the library using an absolute path should help https://tickets.puppetlabs.com/browse/SERVER-973?focusedCommentId=352751&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-352751 Note, any changes to util.rb will still result in horrible environment isolation issues. A full fix would involve implementing @trevor-vaughan's complete metaprogramming solution documented here. https://www.onyxpoint.com/fixing-the-client-side-of-multi-tenancy-in-the-puppet-server util.rb is somewhat more complicated than the example demonstrated, so I've left that well alone for now. Fixes voxpupuli#320
cegeka-jenkins
pushed a commit
to cegeka/puppet-archive
that referenced
this issue
Mar 26, 2021
This doesn't seem to have been neccessary for all users and probably depends on how puppetserver has `ruby-load-path` configured. See https://tickets.puppetlabs.com/browse/SERVER-973?focusedCommentId=224547&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-224547 Requiring the library using an absolute path should help https://tickets.puppetlabs.com/browse/SERVER-973?focusedCommentId=352751&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-352751 Note, any changes to util.rb will still result in horrible environment isolation issues. A full fix would involve implementing @trevor-vaughan's complete metaprogramming solution documented here. https://www.onyxpoint.com/fixing-the-client-side-of-multi-tenancy-in-the-puppet-server util.rb is somewhat more complicated than the example demonstrated, so I've left that well alone for now. Fixes voxpupuli#320
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thats somehow annoying .. I cant progress with my work at the moment ..
Whats wrong here ?
[root@qa5 disk2]# puppet agent -t --server puppet --environment cm Info: Using configured environment 'cm' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not autoload puppet/parser/functions/artifactory_sha1: no such file to load -- puppet_x/bodeco/util at /etc/puppetlabs/code/modules/archive/manifests/artifactory.pp:103:14 at /etc/puppetlabs/code/modules/our_application/manifests/deployer.pp:53 on node qa5 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run[root@qa5 disk2]# puppet agent --version
5.3.3
The text was updated successfully, but these errors were encountered: