unnecessary rubygems upgrades to latest version about chef_client_updater HOT 2 CLOSED

More details about how the terrible chain of events this issue triggered in my case. My application recipe (simplified) contains a chef_client_updater resource to maintain a specific Chef-Client version and a gem_package resource to maintain a specific Bundler version:

chef_client_updater 'install' do
  version '12.7.2'
end
gem_package 'bundler' do
  action :upgrade
  version '1.16.1'
end

This worked fine, until it mysteriously broke one day. Further testing showed that Bundler was no longer being installed to the system ruby.

It turns out that chef_client_updater had started upgrading embedded Rubygems to 2.7.5 on its release, which contained an upgrade to the default-vendored Bundler to version 1.16.1, which was equal to my gem_package's target version . This triggered a long-lived bug in Chef's gem_package chef/chef#3363 which incorrectly adds embedded-Chef's default rubygems to the system-rubygem's version-list when checking if a new version needs to be installed, which skipped the install.

from chef_client_updater.

This should be fixed in 3.3.2

from chef_client_updater.