Red Hat Bugzilla – Bug 853006
Tip information does not show completely in firstboot's Subscription Registration page
Last modified: 2016-09-19 22:27:54 EDT
Description of problem:
Tip information does not show completely in firstboot's Subscription Registration page,
when register and auto subscribe the system with an account which have no subscriptions to subscribe.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. prepare an account without any subscriptions to subscribe - in my case,
I used "stage_test_26" to register to RHEL5.9 Server.
2. Go into firstboot when install a new system or by following steps in a existing system:
2.1 open file /etc/sysconfig/firstboot, then switch the option "RUN_FISRTBOOT" from NO to YES
2.2 reboot the system
3. click "Forward" button until the "Choose Server" page shows
3. make sure the option "Red Hat subscription Management" is selected and click "Forward"
4. input the account's username and password,
and make sure the "Manually assign subscriptions after registration" is not selected, then click "Forward"
A "Subscription Registration" page will show to tell you that no service levels will cover
all installed products. but the message is too long so that it goes out of the screen.
The message show completely and correctly.
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 614265 [details]
Screenshot show the bug
Fixed in subscription-manager.git master: f27481ed85b851be4431cf6254ea35d03f261433
awood will pull into 5.9 branches.
Created attachment 623770 [details]
The "No service levels will cover..." tip is now left justified and does NOT run off the screen.
[root@jsefler-rhel59 ~]# rpm -q subscription-manager-firstboot firstboot
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.