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 1443570 - [RFE] Please remove reference to retired article in subscription-manager man page
Summary: [RFE] Please remove reference to retired article in subscription-manager man ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.3
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-19 13:37 UTC by Rick Dixon
Modified: 2021-09-09 12:15 UTC (History)
5 users (show)

Fixed In Version: subscription-manager-1.20.2-1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 09:49:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin subscription-manager pull 1647 0 None None None 2017-06-02 07:26:25 UTC
Red Hat Product Errata RHBA-2018:0681 0 None None None 2018-04-10 09:49:28 UTC

Description Rick Dixon 2017-04-19 13:37:15 UTC 
The man page for subscription-manager currently references a retired article for disabling location-aware updates:

---
NETWORK INFORMATION
The subscription-manager tool uses outgoing HTTPS requests. In the default configuration  it  will  use  HTTPS  on  port  443  to  the  subscription servers subscription.rhsm.redhat.com and to the content delivery service cdn.redhat.com.

For information about the network addresses that subscription-manager and  the  subscription-manager yum plugin use see https://access.redhat.com/site/articles/414963
---

The article has been retired and contains a private note:

---
KCS solution: https://access.redhat.com/site/solutions/59586

I've retired the article in favor of the solution at this point, because previous the solution linked to the article, which linked to the docs. I've updated the solution to include the link to the docs along with the information found here to eliminate one step for customers.
---

Can we update the man page to link to the KCS rather than the retired article?
Comment 2 Rick Dixon 2017-04-19 13:40:49 UTC 
Follow-up:  I should note that customers who follow the current link in the man page land on a page stating "Access Denied" with no redirection. To preserve a positivie customer experience, perhaps a temporary redirect to the KCS article until the man page can be updated would be helpful.
Comment 3 Nikola Forró 2017-04-19 14:06:23 UTC 
subscription-manager.8 man page is part of subscription-manager component, not man-pages:

$ rpm -qf $(man -w subscription-manager)
subscription-manager-1.17.15-1.el7.x86_64
Comment 6 Rehana 2017-11-09 12:08:45 UTC 
Reproducing the failure:
========================
subscription-manager: 1.19.21-1.el7
python-rhsm: 1.19.9-1.el7

[root@dhcp35-85 ~]# man subscription-manager | grep https://access.redhat.com/site/articles/414963 -B5

NETWORK INFORMATION
       The  subscription-manager  tool  uses  outgoing HTTPS requests. In the default configuration it will use HTTPS on port 443 to the subscription servers subscription.rhsm.redhat.com and to the content
       delivery service cdn.redhat.com.

       For information about the network addresses that subscription-manager and the subscription-manager yum plugin use see https://access.redhat.com/site/articles/414963

Retesting on :
==============
subscription management server: 2.0.43-1
subscription management rules: 5.26
subscription-manager: 1.20.5-1.el7

[root@ibm-x3650m4-01-vm-09 ~]# man subscription-manager | grep https://access.redhat.com/site/solutions/59586 -A10 -B5

NETWORK INFORMATION
       The subscription-manager tool uses outgoing HTTPS requests. In the default configuration it will use HTTPS on port 443 to the subscription servers subscription.rhsm.redhat.com  and  to  the  content
       delivery service cdn.redhat.com.

       For information about the network addresses that subscription-manager and the subscription-manager yum plugin use see https://access.redhat.com/site/solutions/59586


Observed that now the article link is updated "https://access.redhat.com/site/solutions/59586" instead of "https://access.redhat.com/site/articles/414963"


Marking as Verified!!
Comment 9 errata-xmlrpc 2018-04-10 09:49:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0681
Note You need to log in before you can comment on or make changes to this bug.