Bug 1443570

Summary:	[RFE] Please remove reference to retired article in subscription-manager man page
Product:	Red Hat Enterprise Linux 7	Reporter:	Rick Dixon <rdixon>
Component:	subscription-manager	Assignee:	Jiri Hnidek <jhnidek>
Status:	CLOSED ERRATA	QA Contact:	John Sefler <jsefler>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	jhnidek, khowell, redakkan, rjerrido, skallesh
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	subscription-manager-1.20.2-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 09:49:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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