Project

General

Profile

Feature #19477

Custom EPEL product is not integrated seamlessly

Added by Lukas Zapletal about 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Hey,

when you add RHEL product, Satellite automatically detect RHEL version and add appropriate version into redhat.repo, but when using EPEL custom product, this is not possible and users must create custom activation keys like ak-epel-6 and ak-epel-7 to differentiate between versions.

It would be nice to offer them some level of integration so this is more seamless. Most of RHEL users use EPEL repositories.

History

#1 Updated by Justin Sherrill about 2 years ago

  • Legacy Backlogs Release (now unused) set to 114

Also available in: Atom PDF