Description of problem:
We still refer to Red Hat Network and Red Hat Network account logins within Subscription-Manger. It is my understanding that Portal logins are just considered Red Hat accounts now.
Update: "Red Hat Network account" -> "Red Hat account".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Subscription-Manager
2a. Look at the system registration window
2b. Alternatively, look at the Entitlement Platform Registration screen in firstboot
Could impact the initial firstboot screens as well. Set Up Software and Choose Server both contain references to RHN and RHN accounts. Not sure if we're ready to axe RHN references entirely, but I think we should update the RHN account terminology at the least.
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
Created attachment 594228 [details]
Red Hat account firstboot
Testing with versions:
Attached shows that this has changed in firstboot.
Created attachment 594229 [details]
Red Hat account gui
Attached shows this has changed in the registration dialog in the gui as well.
There is an instance of a the old terminology in the gnome help window for subscription-manager-gui:
Projects/subscription-manager|:master ✓ ❯ grep -i -r "Red Hat Network account" . | grep -v \#
./docs/subscription-manager.xml: For infrastructures which use Red Hat's hosted subscription and content delivery network, all that is required to register the system is the username and password of the Red Hat Network account.
This should be changed... throwing back.
7c2395200 master 1.0.5+
Created attachment 595108 [details]
red hat account help window
Tested with versions:
As shown in screenshot, this has been corrected.
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.