-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not autoload puppet/parser/functions/artifactory_sha1 #212
Comments
@antgel many thanks for reporting this issue. Can you check that you are running on modern puppet agent and server version (4 or 5)? Which version of the archive module are you using? |
Being this an issue with upstream archive module we can't do much about it, if not removing all dependencies of this module on default psick (many other modules use it anyway). |
Note to myself: verify if this is solved by adding archive module to the dependencies in metadata.json of puppet-psick module |
Adding something like: Still reluctant to add this as a hard dependency. Worth checking how much archive is actually used in psick module |
I think we've been here before, but it happened again on the second puppet run on a Jenkins server. Can a solution or workaround be found?
ubuntu@puppetagent:~$ sudo puppet agent --test
Info: Using configured environment 'production'
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/environments/production/modules/tp/manifests/conf.pp:273:21 at /etc/puppetlabs/code/environments/production/modules/psick/manifests/postfix/tp.pp:88 on node puppetagent.sandbox.graduway.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
The text was updated successfully, but these errors were encountered: