Bug 191530 - up2date --register does not check if a system is already registered; need --nox
Summary: up2date --register does not check if a system is already registered; need --nox
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Brandon Perkins
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-12 19:08 UTC by Beth Nackashi
Modified: 2008-10-17 19:39 UTC (History)
0 users

Clone Of:
Last Closed: 2007-10-19 18:44:18 UTC

Attachments (Terms of Use)

Description Beth Nackashi 2006-05-12 19:08:08 UTC
Description of problem:
up2date --register/rhn_register does not check if a system is already registered
unless you use the --nox option.  If you invoke up2date --nox --register or
rhn_register --nox, you will get a message saying "This system appears to
already be registered.  Continue anyway?"  Not so without the --nox option.

It shouldn't matter whether or not you're using the GUI or the TUI, you should
be informed if the system is already registered. 

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

How reproducible:

Steps to Reproduce:
1.  Register a system.
2.  Run up2date --register.  GUI pops up with no warning that the system is
already registered.
3.  Run up2date --register --nox.  TUI gives a warning.
Actual results:

Expected results:
User is warned that the system is already registered, regardless of --nox in the
command line.

Additional info:

Comment 2 Red Hat Bugzilla 2007-04-12 00:41:33 UTC
User bnackash@redhat.com's account has been closed

Comment 3 RHEL Product and Program Management 2007-10-19 18:44:18 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:
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.