Could not find recipe epel for cookbook yum

Chef Infra (archive)
1

I’m having a new chef-client issue, it was working fine yesterday, but
now, any chef run gives this error:

chef-client

Starting Chef Client, version 11.6.0
resolving cookbooks for run list: [“base”, “web”, “logging”, “app-ctscom”]
Synchronizing Cookbooks:

  • sudo
  • users
  • line
  • nfs
  • yum
  • windows
  • openssl
  • apt
  • couchbase
  • iis
  • build-essential
  • xml
  • yum-epel
  • mysql
  • php
  • drush
  • chef-varnish
  • apache2
  • zabbix
  • app-ctscom
  • firewall
  • ufw
  • xfs
  • aws
  • postgresql
  • database
  • logging
  • web
  • centrifydc
  • runit
  • chef_handler
  • dmg
  • git
  • logrotate
  • cron
  • chef-client
  • ntp
  • base
    Compiling Cookbooks…

================================================================================
Recipe Compile Error

Chef::Exceptions::RecipeNotFound

could not find recipe epel for cookbook yum

[2014-01-18T22:40:55-06:00] ERROR: Running exception handlers
[2014-01-18T22:40:55-06:00] ERROR: Exception handlers complete
[2014-01-18T22:40:55-06:00] FATAL: Stacktrace dumped to
/var/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated
[2014-01-18T22:40:55-06:00] FATAL:
Chef::Exceptions::ChildConvergeError: Chef run process exited
unsuccessfully (exit code 1)

I’m getting this on all my QA nodes, so I took yum and yum::epel out
of the cookbooks too, restarted chef-server, same issue.

On irc #chef, atompngn told me "you pulled in yum 3.0 in some
cookbook, possibly have a cookbook that depends on ~> 2.0 and ~> 3.0
of yum, ‘git grep yum::epel’, and change to ‘yum-epel’

So in my Berksfile I did

cookbook ‘yum’, ‘~>2.0’

and commented out the yum::epel from the cookbook - then ran berks in;
berks up, but chef-client still gives the same error.

how can I find out if yum is a dependency on another cookbook that
might need epel? Wouldn’t the Berksfile declaration take care of this?

http://philcryer.com/

2

If you’re using Berkshelf, try grepping for ‘yum::epel’ and 'yum-epel’
in the berkshelf store to track down your dependency conflict.

Eric G. Wolfe
Senior Linux Administrator,
IT Infrastructure Systems

Marshall University Computing Services
Drinko Library 428-K
One John Marshall Dr.
Huntington, WV 25755
Phone: 304.942.3970
Email: eric.wolfe@marshall.edu

History books which contain no lies are extremely dull.

On 01/19/2014 01:10 AM, Phil Cryer wrote:

I’m having a new chef-client issue, it was working fine yesterday, but
now, any chef run gives this error:

chef-client

Starting Chef Client, version 11.6.0
resolving cookbooks for run list: [“base”, “web”, “logging”, “app-ctscom”]
Synchronizing Cookbooks:

  • sudo
  • users
  • line
  • nfs
  • yum
  • windows
  • openssl
  • apt
  • couchbase
  • iis
  • build-essential
  • xml
  • yum-epel
  • mysql
  • php
  • drush
  • chef-varnish
  • apache2
  • zabbix
  • app-ctscom
  • firewall
  • ufw
  • xfs
  • aws
  • postgresql
  • database
  • logging
  • web
  • centrifydc
  • runit
  • chef_handler
  • dmg
  • git
  • logrotate
  • cron
  • chef-client
  • ntp
  • base
    Compiling Cookbooks…

================================================================================
Recipe Compile Error

Chef::Exceptions::RecipeNotFound

could not find recipe epel for cookbook yum

[2014-01-18T22:40:55-06:00] ERROR: Running exception handlers
[2014-01-18T22:40:55-06:00] ERROR: Exception handlers complete
[2014-01-18T22:40:55-06:00] FATAL: Stacktrace dumped to
/var/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated
[2014-01-18T22:40:55-06:00] FATAL:
Chef::Exceptions::ChildConvergeError: Chef run process exited
unsuccessfully (exit code 1)

I’m getting this on all my QA nodes, so I took yum and yum::epel out
of the cookbooks too, restarted chef-server, same issue.

On irc #chef, atompngn told me "you pulled in yum 3.0 in some
cookbook, possibly have a cookbook that depends on ~> 2.0 and ~> 3.0
of yum, ‘git grep yum::epel’, and change to ‘yum-epel’

So in my Berksfile I did

cookbook ‘yum’, ‘~>2.0’

and commented out the yum::epel from the cookbook - then ran berks in;
berks up, but chef-client still gives the same error.

how can I find out if yum is a dependency on another cookbook that
might need epel? Wouldn’t the Berksfile declaration take care of this?