When the chef-rundeck gem is installed, it pulls in the chef gem as a dependency, causing Chef to be installed into the system Ruby and installed into /usr/local/bin. This pathing causes it to be the default version of chef-client, ohai, etc. in most cases; that, in turn, causes unpredictable behavior at best and completely breaks Chef at worst.
Installing the chef-rundeck gem using the chef_gem resource instead of gem_package will cause it to be installed into whatever Ruby is currently used for Chef, preventing multiple Chefs from being installed on the system.
When the chef-rundeck gem is installed, it pulls in the chef gem as a dependency, causing Chef to be installed into the system Ruby and installed into /usr/local/bin. This pathing causes it to be the default version of
chef-client
,ohai
, etc. in most cases; that, in turn, causes unpredictable behavior at best and completely breaks Chef at worst.Installing the chef-rundeck gem using the
chef_gem
resource instead ofgem_package
will cause it to be installed into whatever Ruby is currently used for Chef, preventing multiple Chefs from being installed on the system.