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.
Bug 891415 - [RFE] yum repolist should state specifically where a system is getting updates from
Summary: [RFE] yum repolist should state specifically where a system is getting update...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-02 21:24 UTC by Og Maciel
Modified: 2013-01-03 17:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-03 17:58:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Og Maciel 2013-01-02 21:24:40 UTC
Description of problem:

Having migrated a system using RHN Classic to a self hosted SAM instance, I subscribed to one of the available subscriptions and then from the client ran yum repolist. The output claimed that the client was receiving updates from Red Hat Subscription Management. I found that to be misleading and expected to see my SAM instance listed as the source of updates.

Version-Release number of selected component (if applicable):

* subscription-manager-1.1.18-1.el6.x86_64
* subscription-manager-migration-data-1.12.2.6-1.el6.noarch
* subscription-manager-migration-1.1.18-1.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Register a client to a SAM instance
2. Run yum repolist
3.
  
Actual results:

This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.

Expected results:

I think that if we could replace "Red Hat Subscription Management" with "<SAM FQDN>" may make more sense.

Additional info:

Comment 2 Bryan Kearney 2013-01-03 17:58:04 UTC
This text has been approved by the platform group.


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