You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chef-ingredient uses the RPM provider to install packages from a file or remote URL on RHEL. I suspect - though I have no evidence of this claim - the RPM provider was chosen rather than the Yum provider in order to work around an upstream bug that prevented the Yum provider from installing packages from local paths. However, that bug has been patched now, I think it's generally bad practice to use RPM when Yum is the primary package manager and can do the job just as well, and I have noticed some issues with using RPM to install packages on a Yum-based system (package databases getting out of sync, SELinux contexts getting screwed up, etc.). So consider this a request to switch to the Yum provider for RHEL (and probably SuSE as well, though I don't have a SuSE box to test on). :)
The text was updated successfully, but these errors were encountered:
Cookbook version
2.1.3
Chef-client version
12.17.44
Platform Details
RHEL 7
Scenario:
chef-ingredient uses the RPM provider to install packages from a file or remote URL on RHEL. I suspect - though I have no evidence of this claim - the RPM provider was chosen rather than the Yum provider in order to work around an upstream bug that prevented the Yum provider from installing packages from local paths. However, that bug has been patched now, I think it's generally bad practice to use RPM when Yum is the primary package manager and can do the job just as well, and I have noticed some issues with using RPM to install packages on a Yum-based system (package databases getting out of sync, SELinux contexts getting screwed up, etc.). So consider this a request to switch to the Yum provider for RHEL (and probably SuSE as well, though I don't have a SuSE box to test on). :)
The text was updated successfully, but these errors were encountered: