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

Switch to Chef::Provider::Package::Yum on RHEL. #181

Closed
jayhendren opened this issue Jul 17, 2017 · 0 comments
Closed

Switch to Chef::Provider::Package::Yum on RHEL. #181

jayhendren opened this issue Jul 17, 2017 · 0 comments

Comments

@jayhendren
Copy link
Contributor

jayhendren commented Jul 17, 2017

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). :)

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

1 participant