Red Hat Bugzilla – Bug 191530
up2date --register does not check if a system is already registered; need --nox
Last modified: 2008-10-17 15:39:19 EDT
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):
Steps to Reproduce:
1. Register a system.
2. Run up2date --register. GUI pops up with no warning that the system is
3. Run up2date --register --nox. TUI gives a warning.
User is warned that the system is already registered, regardless of --nox in the
User firstname.lastname@example.org's account has been closed
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.