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 replaced. 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." Thanks, John Version-Release number of selected component (if applicable): How reproducible: Always. 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:
Move to Bugzilla Bug 218517: RHN 510 Hosted Triage Tracker.
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?
User bnackash's account has been closed
User jslagle's account has been closed
*** This bug has been marked as a duplicate of bug 248044 ***