Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 161565 - [RFE] rhnreg_ks options to delete/replace old profiles on RHN
[RFE] rhnreg_ks options to delete/replace old profiles on RHN
Status: CLOSED DUPLICATE of bug 248044
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Clifford Perry
Brandon Perkins
Depends On:
Blocks: 218517
  Show dependency treegraph
Reported: 2005-06-24 10:45 EDT by John T. Rose
Modified: 2008-11-21 15:31 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-21 15:31:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John T. Rose 2005-06-24 10:45:07 EDT
Description of problem:

We currently have around 400 user accounts on RHN. Not an insignificant number
of these users have had trouble with re-registering machines with their
activation keys. To reduce the support overhead of dealing with them
individually we eventually added the --force option to our bootstrap script,
which I believe is something you also include in your example bootstrap script now.

This leads to the problem of users registering, messing things up, registering
again, and so on cluttering up the corporate RHN account with lots of inactive
profiles. While I know there are many issues with automatic deletion of old
profiles (some machines want more than one, some machines have profiles on
multiple rhn accounts, etc.) the most common situation is that a user is
re-registering his machine on a single RHN account and really wants the profile

So I would like to request that options such as --delete and/or --replace be
added to rhnreg_ks to ease this problem at least in the common cases. In the
more complicated cases such as those mentioned above it would be fine to say
"sorry but we can't perform this operation."


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

How reproducible:


Steps to Reproduce:
1. rhnreg_ks a new system with an activaton key
2. run rhnreg_ks --force with an activation key on the same system
Actual results:

See two profiles on RHN, one of which is simply cruft. We would like to instead
run rhnreg_ks --force --replace with the result that only the newly created
profile will exist on RHN after the registration is complete.

Expected results:

Additional info:
Comment 2 Brandon Perkins 2007-03-12 13:00:39 EDT
Move to Bugzilla Bug 218517: RHN 510 Hosted Triage Tracker.
Comment 3 John T. Rose 2007-03-27 22:45:29 EDT
Since I requested this enhancement around 2 years ago I'm curious but am not
allowed to see Bug 218517. Can you let me know here or elsewhere what decision
was made or what the meaning of the previous comment is please?
Comment 4 Red Hat Bugzilla 2007-04-11 20:15:54 EDT
User bnackash@redhat.com's account has been closed
Comment 6 Red Hat Bugzilla 2007-10-25 20:47:58 EDT
User jslagle@redhat.com's account has been closed
Comment 7 Jeremy West 2008-11-21 15:31:12 EST

*** This bug has been marked as a duplicate of bug 248044 ***

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