You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This runs the instance.sh script on the node (via Choria queue). But the Choria controller gets the following error: choria.tasks/task-error: The task errored with a code 1 {"status":"failure"}
According to the /tmp/bolt-run log Error: Evaluation Error: Unknown function: 'gcompute_task_load_params'. (line: 17, column: 11) on node infrastructure.internal
If I manually store the gauth and gcompute modules under /etc/puppetlabs/code/modules/ everything is working well. But I think this is not the target of a master/client setup. It probably should use the scripts from the master, which are stored under /opt/puppetlabs/puppet/cache/lib/
I've a puppetserver (6.1x) with a node connected, provisioning GCP. Which is working pretty well.
I tried now to orchestrate the instances with Puppet Tasks (based on Choria) for this node.
mco tasks run gcompute::instance --credential /root/credential.json --name testing --ensure present --project projectname --zone europe-west3-c -I infrastructurenode.internalThis runs the
instance.shscript on the node (via Choria queue). But the Choria controller gets the following error:choria.tasks/task-error: The task errored with a code 1 {"status":"failure"}According to the
/tmp/bolt-runlogError: Evaluation Error: Unknown function: 'gcompute_task_load_params'. (line: 17, column: 11) on node infrastructure.internalIf I manually store the gauth and gcompute modules under
/etc/puppetlabs/code/modules/everything is working well. But I think this is not the target of a master/client setup. It probably should use the scripts from the master, which are stored under/opt/puppetlabs/puppet/cache/lib/