Skip to content
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

r10k does not install via Puppet on Puppet 4 #258

Closed
Wicaeed opened this issue Nov 24, 2015 · 1 comment
Closed

r10k does not install via Puppet on Puppet 4 #258

Wicaeed opened this issue Nov 24, 2015 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@Wicaeed
Copy link

Wicaeed commented Nov 24, 2015

Trying to set up a new Puppet Master on Puppet 4.2.3 and see the following error when Puppet tries to install r10k:

root@puppet-master:/etc/puppetlabs# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for puppet-master.sc1.lan
Info: Applying configuration version '1448333411'
Error: Could not set 'file' on ensure: No such file or directory @ dir_s_rmdir - /etc/puppetlabs/r10k/r10k.yaml20151123-14043-1xq6uu7.lock at 92:/etc/puppetlabs/code/environments/production/modules/r10k/manifests/config.pp
Error: Could not set 'file' on ensure: No such file or directory @ dir_s_rmdir - /etc/puppetlabs/r10k/r10k.yaml20151123-14043-1xq6uu7.lock at 92:/etc/puppetlabs/code/environments/production/modules/r10k/manifests/config.pp
Wrapped exception:
No such file or directory @ dir_s_rmdir - /etc/puppetlabs/r10k/r10k.yaml20151123-14043-1xq6uu7.lock
Error: /Stage[main]/R10k::Config/File[r10k.yaml]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory @ dir_s_rmdir - /etc/puppetlabs/r10k/r10k.yaml20151123-14043-1xq6uu7.lock at 92:/etc/puppetlabs/code/environments/production/modules/r10k/manifests/config.pp
Notice: Applied catalog in 0.44 seconds

Was able to fix the issue by hand creating the /etc/puppetlabs/r10k folder and assinging permissions to the puppet user.

The next run was successful.

root@puppet-master:/etc/puppetlabs# ls -lah
total 32K
drwxr-xr-x  8 puppet   puppet    4.0K Nov 23 18:59 .
drwxr-xr-x 99 root     root      4.0K Nov 20 06:35 ..
drwxr-xr-x  4 puppet   sysadmins 4.0K Nov 17 18:25 code
lrwxrwxrwx  1 root     root        55 Nov 11 15:56 hiera.yaml -> /etc/puppetlabs/code/environments/production/hiera.yaml
drwxr-xr-x  2 puppet   sysadmins 4.0K Nov  4 12:32 mcollective
drwxr-xr-x  3 puppet   sysadmins 4.0K Nov 23 17:24 puppet
drwxr-xr-x  4 puppetdb sysadmins 4.0K Nov 10 18:35 puppetdb
drwxr-xr-x  3 puppet   sysadmins 4.0K Nov  4 12:32 puppetserver
drwxr-xr-x  2 root     root      4.0K Nov 23 18:59 r10k
root@puppet-master:/etc/puppetlabs# mkdir r10k
root@puppet-master:/etc/puppetlabs# chown puppet:sysadmins r10k/
root@puppet-master:/etc/puppetlabs# ls -lah
total 32K
drwxr-xr-x  8 puppet   puppet    4.0K Nov 23 18:59 .
drwxr-xr-x 99 root     root      4.0K Nov 20 06:35 ..
drwxr-xr-x  4 puppet   sysadmins 4.0K Nov 17 18:25 code
lrwxrwxrwx  1 root     root        55 Nov 11 15:56 hiera.yaml -> /etc/puppetlabs/code/environments/production/hiera.yaml
drwxr-xr-x  2 puppet   sysadmins 4.0K Nov  4 12:32 mcollective
drwxr-xr-x  3 puppet   sysadmins 4.0K Nov 23 17:24 puppet
drwxr-xr-x  4 puppetdb sysadmins 4.0K Nov 10 18:35 puppetdb
drwxr-xr-x  3 puppet   sysadmins 4.0K Nov  4 12:32 puppetserver
drwxr-xr-x  2 puppet   sysadmins 4.0K Nov 23 18:59 r10k
root@puppet-master:/etc/puppetlabs# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for puppet-master
Info: Applying configuration version '1448333960'
Notice: /Stage[main]/R10k::Config/File[r10k.yaml]/ensure: defined content as '{md5}c1fc620778689e769fe060df9acdec9d'
Notice: Applied catalog in 0.48 seconds
@mmckinst
Copy link
Contributor

This was fixed at https://github.com/acidprime/r10k/pull/242 . This fix was put in the 3.2.0 release on puppetforge on Dec 16, 2015. If you were using the latest module on puppet forge on Nov 23, 2015 it didn't have the fix in it at that time. If you try again now, it should work without doing the manual step.

@rnelson0 rnelson0 added the duplicate This issue or pull request already exists label Jan 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants