Bug 853006 - Tip information does not show completely in firstboot's Subscription Registration page
Summary: Tip information does not show completely in firstboot's Subscription Registra...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: John Sefler
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 771748
TreeView+ depends on / blocked
 
Reported: 2012-08-30 09:00 UTC by xingge
Modified: 2016-09-20 02:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 04:02:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot show the bug (95.10 KB, image/png)
2012-09-19 08:49 UTC, xingge
no flags Details
The "No service levels will cover..." tip is now left justified and does NOT run off the screen. (116.96 KB, image/png)
2012-10-08 22:10 UTC, John Sefler
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0033 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-01-08 08:38:27 UTC

Description xingge 2012-08-30 09:00:22 UTC
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):
subscription-manager-firstboot-1.0.14-1.el5
firstboot-1.4.27.9-1.el5
firstboot-tui-1.4.27.9-1.el5

How reproducible:
always

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"
  
Actual results:
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. 

Expected results:
The message show completely and correctly.

Additional info:

Comment 1 RHEL Program Management 2012-08-30 09:07:25 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 xingge 2012-09-19 08:49:58 UTC
Created attachment 614265 [details]
Screenshot show the bug

Comment 3 Devan Goodwin 2012-10-01 15:57:44 UTC
Fixed in subscription-manager.git master: f27481ed85b851be4431cf6254ea35d03f261433

awood will pull into 5.9 branches.

Comment 6 John Sefler 2012-10-08 22:10:41 UTC
Created attachment 623770 [details]
The "No service levels will cover..." tip is now left justified and does NOT run off the screen.

Verifying Version...
[root@jsefler-rhel59 ~]# rpm -q subscription-manager-firstboot firstboot
subscription-manager-firstboot-1.0.21-1.el5
firstboot-1.4.27.9-1.el5

Comment 8 errata-xmlrpc 2013-01-08 04:02:31 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


Note You need to log in before you can comment on or make changes to this bug.