Bug 847795

Summary:	String Update: redhat_branding.py Updates
Product:	Red Hat Enterprise Linux 5	Reporter:	Matt Reid <mreid>
Component:	subscription-manager	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED ERRATA	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.9	CC:	bkearney, jmolet
Target Milestone:	beta
Target Release:	5.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-08 03:58:48 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:
Bug Depends On:
Bug Blocks:	771748, 827225

Description Matt Reid 2012-08-13 15:12:26 UTC

Description of problem:
This should be the last section of strings that need some tweaking for 5.9. It'd be good to get rid of these final mentions of RHN and Certificate-Based.

1. (replace RHN with Red Hat, remove technology)
"This system has already been registered with RHN using RHN Classic "
"technology." ->
This system has already been registered with Red Hat using RHN Classic.

2. (I'd love to replace this whole string, as the article really only talks about how to fix getting one of these warning messages, and has a link to learn more about the options)
"To learn more about RHN registration and technologies please consult this "
"Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563" ->
To learn how to unregister from either service please consult this
Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563

3. (replace cert-based w/ RHSM, remove technology)
"This system is registered using both RHN Classic technology and RHN "
"Certificate-Based technology." ->
This system is registered using both RHN Classic and Red Hat Subscription Management.

4. (replace SMS w/ RHSM, capitalize Classic)
"RHN classic and subscription management service" ->
RHN Classic and Red Hat Subscription Management

5. (reworked to remove RHN, remove 'except in a few cases')
"Red Hat recommends (except in a few cases) that customers only register with "
"RHN via one method." ->
Red Hat recommends that customers only register to one service.

If you're more comfortable having the last string just be a straight swap, you could simply replace RHN with Red Hat. I think it could use a bit more tweaking than that, but we should at least update the reference to RHN.

A simpler variant of the second message would be to just replace RHN with Red Hat, but that current string seems a little misleading.

Comment 1 RHEL Program Management 2012-08-14 02:07:22 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 2 Bryan Kearney 2012-08-16 13:18:52 UTC

fixed in master at dbb76f8f275964cfe2b8afaf7c9583c4ff6484f6

Comment 4 J.C. Molet 2012-09-20 14:26:50 UTC

Item 1)
Line 13 -  _("This system has already been registered with Red Hat using RHN Classic technology.") + \

'technology' is still present FAILS QA  --> opened in new bug 859090

Item 2)
Line 17: _("To learn how to unregister from either service please consult     this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563")

PASSES QA

Item 3)
Line 23: _("This system is registered using both RHN Classic and Red Hat Subscription Management.")

PASSES QA

Item 4)
Line 23: _("This system is registered using both RHN Classic and Red Hat Subscription Management.")

PASSES QA

Item 5)
Line 25: _("Red Hat recommends that customers only register to one service.")

PASSES QA



Tested against   subscription-manager.x86_64 0:1.0.18-1.el5  (latest in brew)

All cases pass except case 1, which will be addressed in bug 859090 .
Marking VERIFIED.

Comment 6 errata-xmlrpc 2013-01-08 03:58:48 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.

http://rhn.redhat.com/errata/RHBA-2013-0033.html