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
When I add a new module to the Puppetfile I get the below error message
-> Deploying module /etc/puppetlabs/code/environments/production/modules/make\nERROR\t
-> Command exited with non-zero exit code:\nCommand: puppet module --modulepath /etc/puppetlabs/code/environments/production/modules --color false install --version=0.0.5 --force croddy/make\nStderr:\nErrno::ENOENT: No such file or directory - puppet\nExit code: 254\nINFO\t
Running puppet module --modulepath /etc/puppetlabs/code/environments/production/modules --color false install --version=0.0.5 --force croddy/make as root completes successfully. The webhook is running as root. Is there a path I am not passing into my manifest?
I am using commit e584e3a with the below puppet code:
class { 'r10k':
remote => 'puppet-control_repo:githost/puppet-control_repo.git',
git_settings => {
'private_key' => '/etc/puppetlabs/puppetserver/r10kgit',
}
}
class {'r10k::webhook::config':
use_mcollective => false,
github_secret => 'XXXXXXXXXXX',
public_key_path => '/etc/puppetlabs/puppet/ssl/certs/puppet.server.pem',
private_key_path => '/etc/puppetlabs/puppet/ssl/private_keys/puppet.server.pem',
}
class {'r10k::webhook':
use_mcollective => false,
user => 'root',
group => '0',
require => Class['r10k::webhook::config'],
}
Also, running r10k deploy environment -p works successfully.
The text was updated successfully, but these errors were encountered:
When I add a new module to the Puppetfile I get the below error message
Running
puppet module --modulepath /etc/puppetlabs/code/environments/production/modules --color false install --version=0.0.5 --force croddy/make
as root completes successfully. The webhook is running as root. Is there a path I am not passing into my manifest?I am using commit e584e3a with the below puppet code:
Also, running
r10k deploy environment -p
works successfully.The text was updated successfully, but these errors were encountered: