-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
EPEL managed_repo broken #53
Comments
|
It looks like @bastelfreak ran into this a while ago and worked around it by just treating .repo files as the ini files they really are and bypassing the Yumrepo resource type all together. |
The provided settings for the EPEL repos were using the "name" key for the repository description, but this maps to the Puppet namevar, which is the repo ID (aka the name of the file in /etc/yum.repos.d). They should instead be using the key "descr" which is what maps to the "name" value in the repo settings. Fixes issue voxpupuli#53
The provided settings for the EPEL repos were using the "name" key for the repository description, but this maps to the Puppet namevar, which is the repo ID (aka the name of the file in /etc/yum.repos.d). They should instead be using the key "descr" which is what maps to the "name" value in the repo settings. Fixes issue voxpupuli#53
|
I think the I've fixed this in my fork although now I'm having issues with the gpg key. It's trying to read the GPG key from |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Hiera:
Puppet Profile:
What are you seeing
Instead of a a file being created at /etc/repos.d/epel.repo, it is created at "/etc/yum.repos.d/Extra Packages for Enterprise Linux 7 - $basearch.repo".
At that point if you try to add a package from epel, such as glances, the yum command will fail. When trying to run a manual yum install to verify the package exists, you get the error below.
What behaviour did you expect instead
A functional package install with yum from epel. It should have payed attention to the target parameter to Yumrepo.
Output log
Any additional information you'd like to impart
It looks like this isn't the module's fault but rather the core YumRepo Resource Type. In the meantime it can be worked around by treating epel like a custom repo again. The gotcha there is you have to give it a new title suffix such as epel_workaround so it doesn't pick up on the broken definitions inside the module. This also has the limitation that only a single repo definition can be present inside the file.
The text was updated successfully, but these errors were encountered: