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

eyaml gem not installed in PE 2017.2.2 #201

Open
jvelasquez opened this issue Jul 14, 2017 · 1 comment
Open

eyaml gem not installed in PE 2017.2.2 #201

jvelasquez opened this issue Jul 14, 2017 · 1 comment

Comments

@jvelasquez
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: PE 2017.2.2
  • Ruby: ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux]
  • Distribution:
  • Module version: CentOS Linux release 7.3.1611 (Core)

How to reproduce (e.g Puppet code you use)

  class { 'hiera':
    hierarchy       => [
      'virtual/%{::virtual}',
      'nodes/%{::trusted.certname}',
      'common',
    ],
    hiera_yaml      => $hiera_yaml,
    datadir         => '/etc/puppetlabs/code/environments/%{environment}/hieradata',
    owner           => 'pe-puppet',
    group           => 'pe-puppet',
    notify          => Service['pe-puppetserver'],

    ## Configure eyaml
    eyaml           => true,
    # create_keys     => true,
    eyaml_extension => 'yaml',
  }

Puppetfile

forge "http://forge.puppetlabs.com"

mod "puppetlabs/inifile",     '1.6.0'
mod "puppetlabs/stdlib",      '4.17.1'
mod "puppetlabs/concat",      '2.2.1'
mod "puppet/hiera",           '3.0.0'
mod "npwalker/pe_code_manager_webhook",  '2.0.1'
mod "npwalker/pe_metric_curl_cron_jobs", '4.0.0'

mod 'gms',
  :git    => 'https://github.com/abrader/abrader-gms',
  :ref    => 'a5105e95cf0f8b84a143d7a69a83e3ff3d4e02fb'

#mod 'pltraining-rbac',
#  :git    => 'https://github.com/puppetlabs/pltraining-rbac',
#  :ref    => '9a823ff42810988f80a2b65738054a816620d972'

mod 'custom_profile_puppetmaster',
  :git    => 'git',
  :tag    => 'v1.0-beta.1'

What are you seeing

Error saying that I am missing the eyaml gem

What behaviour did you expect instead

The hiera module to install the eyam puppetgem

Output log

[root@ip-172-31-36-6 code]# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for ip-172-31-36-6.eu-west-1.compute.internal
Info: Applying configuration version 'ddb1532057657673bb77a8f7a02af48de89bd5ee'
Notice: /Stage[main]/Puppet_enterprise::Master/Pe_ini_setting[puppetconf environment_timeout setting]/value: value changed 'unlimited' to '0'
Info: /Stage[main]/Puppet_enterprise::Master/Pe_ini_setting[puppetconf environment_timeout setting]: Scheduling refresh of Service[pe-puppetserver]
Error: Could not find command 'eyaml'
Error: /Stage[main]/Hiera::Eyaml/Exec[createkeys]/returns: change from notrun to 0 failed: Could not find command 'eyaml'
Notice: /Stage[main]/Hiera::Eyaml/File[/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Hiera::Eyaml/File[/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem]: Skipping because of failed dependencies
Notice: /Stage[main]/Hiera::Eyaml/File[/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Hiera::Eyaml/File[/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem]: Skipping because of failed dependencies
Notice: /Stage[main]/Hiera/File[/etc/puppetlabs/puppet/hiera.yaml]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Hiera/File[/etc/puppetlabs/puppet/hiera.yaml]: Skipping because of failed dependencies
Notice: /Stage[main]/Hiera/File[/etc/hiera.yaml]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Hiera/File[/etc/hiera.yaml]: Skipping because of failed dependencies
Notice: /Stage[main]/Hiera/Ini_setting[puppet.conf hiera_config main section]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Hiera/Ini_setting[puppet.conf hiera_config main section]: Skipping because of failed dependencies
Notice: /Stage[main]/Custom_profile_puppetmaster/Ini_setting[environment_timeout = unlimited]/value: value changed '0' to 'unlimited'
Info: /Stage[main]/Custom_profile_puppetmaster/Ini_setting[environment_timeout = unlimited]: Scheduling refresh of Service[pe-puppetserver]
Notice: Please Enable Code Manager via hiera with this parameter `puppet_enterprise::profile::master::code_manager_auto_configure`.  If you enabled code manager via the PE Console you may set $force_code_manager_webhook to true.
Notice: /Stage[main]/Pe_code_manager_webhook/Notify[Please Enable Code Manager via hiera with this parameter `puppet_enterprise::profile::master::code_manager_auto_configure`.  If you enabled code manager via the PE Console you may set $force_code_manager_webhook to true.]/message: defined 'message' as 'Please Enable Code Manager via hiera with this parameter `puppet_enterprise::profile::master::code_manager_auto_configure`.  If you enabled code manager via the PE Console you may set $force_code_manager_webhook to true.'
Notice: /Stage[main]/Puppet_enterprise::Master::Puppetserver/Puppet_enterprise::Trapperkeeper::Pe_service[puppetserver]/Service[pe-puppetserver]: Dependency Exec[createkeys] has failures: true
Warning: /Stage[main]/Puppet_enterprise::Master::Puppetserver/Puppet_enterprise::Trapperkeeper::Pe_service[puppetserver]/Service[pe-puppetserver]: Skipping because of failed dependencies
Info: /Stage[main]/Puppet_enterprise::Master::Puppetserver/Puppet_enterprise::Trapperkeeper::Pe_service[puppetserver]/Service[pe-puppetserver]: Unscheduling all events on Service[pe-puppetserver]
Info: Stage[main]: Unscheduling all events on Stage[main]
Notice: Applied catalog in 9.91 seconds

Any additional information you'd like to impart

n/a

@dwtien
Copy link

dwtien commented Jul 27, 2017

I ran to the same issue on PE2017.2.1. I tried rolling back to a snapshot of PE2016.4.3 but still experienced the same problem. I came across the following solution:

voxpupuli/hiera-eyaml#177

Basically, you have to run the gem install twice:

/opt/puppetlabs/puppet/bin/gem install hiera-eyaml
/opt/puppetlabs/bin/puppetserver gem install hiera-eyaml

Following that, a puppet run was successful and keys were created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants