eyaml commands were working but not hiera-eyaml.
the following solved my problem.
default gem install uses the wrong gem environment. puppet uses a different
one.
use /opt/puppet/bin/gem to install hiera-eyaml instead of default
/usr/local/bin/gem
On Thursday, January 2, 2014 4:44:32 PM UTC+1, Kit Plummer wrote:
>
> Hey Werner.
>
> I just added the 'read' permission to the global setting on the installed
> gems' directories after the 'gem install' command. I had to do it for
> hiera-eyaml and the gems that were installed with it.
>
> Kit.
> On Jan 2, 2014 8:39 AM, "Werner Bahlke" <werner...@gmail.com <javascript:>>
> wrote:
>
>> Hi Kit,
>>
>> I am glad you found the cause. Can you tell me a bit more how you
>> resolved it? I probably can figure it out eventually but any hints will be
>> greatly appreciated.
>>
>> Thanks,
>>
>> Werner
>>
>>
>> On Mon, Dec 30, 2013 at 11:17 AM, Kit Plummer <kitpl...@gmail.com
>> <javascript:>> wrote:
>>
>>> Hey Werner. I did resolve my issue. It turned out to be a path issue,
>>> with how the PE’s rubygems installs gems. While the eyaml commands were
>>> working, the directory for the hiera-eyaml (and it’s dependent gems) didn’t
>>> allow the pe-puppet user (global perms) to get to the lib .rb files in the
>>> installed gems.
>>>
>>> It’s a bug and I need to remember to file it.
>>>
>>> Kit
>>>
>>>
>>> ------------------------------------------------------
>>> From: wernerbahlke werner...@gmail.com <javascript:>
>>> Reply: puppet...@googlegroups.com <javascript:>
>>> puppet...@googlegroups.com <javascript:>
>>> Date: December 30, 2013 at 9:12:48 AM
>>> To: puppet...@googlegroups.com <javascript:> puppet...@googlegroups.com
>>> <javascript:>
>>> Subject: [Puppet Users] Re: Problem using hiera-eyaml
>>>
>>> >
>>> > Hi Kit,
>>> >
>>> > Thanks for posting. No, I did not resolve it and have put it on the
>>> > back
>>> > burner. Quite possible that it is a Ruby / gems issue.
>>> >
>>> > Keep us posted if you resolve it before me.
>>> >
>>> > Werner
>>> >
>>> > On Saturday, December 21, 2013 11:13:46 AM UTC-5, Kit Plummer
>>> > wrote:
>>> > >
>>> > > Did you resolve this?
>>> > >
>>> > > I'm having a similar problem. But, I think it is because the eyaml
>>> > > backend isn't getting loaded :) :
>>> > >
>>> > > "Cannot load backend eyaml: cannot load such file --
>>> > > hiera/backend/eyaml_backend"
>>> > >
>>> > > I'm wondering if this is because the Ruby version/Gems that
>>> > are used by PE.
>>> > >
>>> > > On Friday, December 6, 2013 8:10:35 AM UTC-7, wernerbahlke
>>> > wrote:
>>> > >>
>>> > >> I am trying to use hiera-eyaml and have followed the README
>>> > instructions.
>>> > >>
>>> > >> eyaml seems to work, I can encrypt and decrypt files and passwords.
>>> > >>
>>> > >> I can also use hiera -c to get at an encrypted value like so:
>>> > >>
>>> > >> hiera -c /etc/puppetlabs/puppet/hiera.yaml rootpwd
>>> > >>
>>> > >> But when running this simple test module it fails with cannot
>>> > find the
>>> > >> data item rootpwd defined in hieradata/defaults.eyaml.
>>> > >>
>>> > >> class test {
>>> > >> $test = hiera('test')
>>> > >> $rootpwd = hiera('rootpwd')
>>> > >> notify { "Test: ${test}": }
>>> > >> }
>>> > >> If I just have the test variable defined in defaults.yaml it
>>> > works fine.
>>> > >> So it cannot find the defaults.eyaml file.
>>> > >>
>>> > >> Here is my hiera.yaml:
>>> > >> ------------------------------
>>> > >>
>>> > >> :backends:
>>> > >>
>>> > >> - yaml
>>> > >> - eyaml
>>> > >> - :hierarchy:
>>> > >> - defaults
>>> > >> - "%{clientcert}"
>>> > >> - "%{environment}"
>>> > >> - global
>>> > >> - :yaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
>>> > >> - :eyaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
>>> > >> - :pkcs7_private_key:
>>> > >> /etc/puppetlabs/puppet/secure/keys/private_key.pkcs7.pem
>>> > >> - :pkcs7_public_key:
>>> > >> /etc/puppetlabs/puppet/secure/keys/public_key.pkcs7.pem
>>> > >>
>>> > >> And my defaults.eyaml file:
>>> > >> ------------------------------
>>> > >>
>>> > >> rootpwd: >
>>> > >>
>>> ENC[PKCS7,MIIBeQYJKoZIhvcNAQcDoIIBajCCAWYCAQAxggEhMIIBHQIBADAFMAACAQAwDQYJKoZIhvcNAQE
>>> > >> ...]
>>> > >> Any hints will be greatly appreciated.
>>> > >>
>>> > >> I am running Puppet Enterprise 3.1.0 on Ubuntu 12.04.
>>> > >>
>>> > >
>>> >
>>> > --
>>> > You received this message because you are subscribed to a topic
>>> > in the Google Groups "Puppet Users" group.
>>> > To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/puppet-users/qpia1_TR2dI/unsubscribe.
>>> > To unsubscribe from this group and all its topics, send an email
>>> > to puppet-users...@googlegroups.com <javascript:>.
>>> > To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/eed4dd1d-6fc0-4538-b1c5-1621f78ab509%40googlegroups.com
>>> .
>>> > For more options, visit https://groups.google.com/groups/opt_out.
>>> >
>>>
>>>
>>
>>
>> --
>> *Werner Bahlke <http://wernerbahlke.com/> | T: 503-438-9466 | Skype:
>> wernerbahlke*
>> <http://www.linkedin.com/in/wernerbahlke>
>>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f343eb17-2d87-4dd9-abb4-f30e8f9a65fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
