Open berndmweber opened 11 years ago
Check your permissions on /etc/puppet/gpgdata and ensure the owner and group match the user that is running the puppet server.
In my case I am running the puppet master as the puppet user so I needed to do the following.
chown -R puppet:root /etc/puppet/keyrings
chmod 0770 /etc/puppet/keyrings
This worked for me and I was having the very same issues as you described above. Hope this helps.
Hey,
Don't seem to be able to get this to work. I read the earlier bug report but that didn't seem to solve my problems. I changed the owner of /etc/puppet/gpgdata to puppet and made sure the permissions are 750 on the directory and 640 on all files inside. When I execute
hiera -d -c hiera.yaml mysql:server:root_passwd
either as root or puppet I get the correct value back:Whenever I try to run this through the puppet agent it fails:
I'm wondering if I'm even installing this correctly. I used
gem install hiera-gpg
. I can see it and the hiera gem fine in the /var/lig/gems directory. But I'm suspecting that puppet is using it's own hiera version in /usr/lib/ruby/vendor_ruby ?! Which would explain the issues I'm seeing.Some more information: hiera.yaml:
The call to hiera is in manifests/site.pp:
All my setup can be found here: https://github.com/berndmweber/open-source-puppet-master/tree/master/modules/puppet
Any feedback is appreciated!