Bug 191544 - Back option doesn't work on Step 3 panel when using up2date --nox --register
Summary: Back option doesn't work on Step 3 panel when using up2date --nox --register
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-12 19:46 UTC by Beth Nackashi
Modified: 2008-10-17 19:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:44:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Beth Nackashi 2006-05-12 19:46:36 UTC 
Description of problem:
On "Step 3" panel of up2date --nox --register, Back option doesn't work.

Version-Release number of selected component (if applicable):
up2date-4.4.69-8

How reproducible:
always

Steps to Reproduce:
1.  Run up2date --nox --register.
2.  On the Step 3 panel (the one with the system/hardware profile information),
select "Back".

Actual results:
same panel loads

Expected results:
return to previous panel

Additional info:
no information is given in /var/log/up2date
Comment 2 Red Hat Bugzilla 2007-04-12 00:41:51 UTC 
User bnackash's account has been closed
Comment 3 RHEL Program Management 2007-10-19 18:44:12 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.
Note You need to log in before you can comment on or make changes to this bug.