Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1756330 - [RFE] Make it possible to associate release version with a custom repository
Summary: [RFE] Make it possible to associate release version with a custom repository
Keywords:
Status: CLOSED DUPLICATE of bug 1526564
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.5.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-27 12:08 UTC by Jan Senkyrik
Modified: 2019-10-04 14:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-04 14:14:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Senkyrik 2019-09-27 12:08:02 UTC
Description of problem:
Locking RHEL system to a certain release version doesn't affect custom products because the URL path is missing the required yum variables:

Custom repo:
~~~
[Default_Organization_EPEL7_epel7]
metadata_expire = 1
sslclientcert = /etc/pki/entitlement/1673524737023542242.pem
baseurl = https://satellite.example.com/pulp/repos/Default_Organization/Library/custom/EPEL7/epel7
sslverify = 1
name = epel7
sslclientkey = /etc/pki/entitlement/1673524737023542242-key.pem
gpgkey = https://provisioning.sysmgmt.lan/katello/api/v2/repositories/254/gpg_key_content
enabled = 1
sslcacert = /etc/rhsm/ca/katello-server-ca.pem
gpgcheck = 1
~~~

Red Hat repo:
~~~
[rhel-7-server-rpms]
metadata_expire = 1
sslclientcert = /etc/pki/entitlement/1504396905308848865.pem
baseurl = https://satellite.example.com/pulp/repos/Default_Organization/Library/content/dist/rhel/server/7/$releasever/$basearch/os
ui_repoid_vars = releasever basearch
sslverify = 1
name = Red Hat Enterprise Linux 7 Server (RPMs)
sslclientkey = /etc/pki/entitlement/1504396905308848865-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/katello-server-ca.pem
gpgcheck = 1
~~~


Thanks,
Jan

Comment 4 Rich Jerrido 2019-10-04 14:14:19 UTC

*** This bug has been marked as a duplicate of bug 1526564 ***


Note You need to log in before you can comment on or make changes to this bug.