Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Description of problem:
Consider the following setup with an Atomic Host
Atomic Host is registered to RH Satellite and is consuming content from Sat for upgrades. Now the user runs "docker run -it registry.access.redhat.com/rhel7" and tries to "yum install screen". This is going to cause a 404.
Basic problem here is that in a Satellite the URL used for consuming yum content is different from url used for "atomic upgrade". However subscription manager has only one 'baseurl' entry.
Sample rhsm.conf configuration for RHEL using satellite
"""
# Unified Entitlement Platform Configuration
[server]
# Server hostname:
hostname = .....
.....
[rhsm]
# Content base URL:
baseurl= https://sat-fqdn.com/pulp/repos/
.......
"""
Sample rhsm.conf configuration for RHELAH using satellite
"""
# Unified Entitlement Platform Configuration
[server]
# Server hostname:
hostname = .....
.....
[rhsm]
# Content base URL:
baseurl= https://sat-fqdn.com/pulp/ostree/web/
.......
"""
A clean approach here would be for subscription manager to have something like
"""
# Unified Entitlement Platform Configuration
[server]
# Server hostname:
hostname = .....
.....
[rhsm]
# Content base URL:
baseurl= https://sat-fqdn.com/pulp/repos
atomic_baseurl= https://sat-fqdn.com/pulp/ostree/web/
.......
""""
This subscirption manager can use atomic_baseurl when setting /etc/ostree/remotes.d/redhat.repo while using baseurl for yum.
Comment 3RHEL Program Management
2020-12-15 07:44:55 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.