Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
yum history is obviously using UID to identify the user in the transaction. It would be better if also the login would be stored. In case the user is deleted and a new one receives the same UID, transtactions performed by the old user are assigned to the new one in the history.
If yum would store also the login, it could compare the login if the current user and inform that the transaction has been done by an already removed user.
I think it is not necessary to store more details about the user, the login is usualy enough to identify the user using other evidence.
Actual results:
1. I have several transactions made by user IlikeMyLongName...
# yum history list
Loaded plugins: refresh-packagekit, rhnplugin
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
189 | <IlikeMyLongNameSoMuchEv | 2011-03-22 08:37 | Erase | 1
188 | <IlikeMyLongNameSoMuchEv | 2011-03-22 08:36 | Install | 1
187 | <IlikeMyLongNameSoMuchEv | 2011-03-22 08:35 | Erase | 1
186 | <IlikeMyLongNameSoMuchEv | 2011-03-22 08:31 | Install | 1
2. Now I delete this user account and add a new acount "myuser" which receives the same uid. I let "myuser" do a new transaction.
# yum history list
Loaded plugins: refresh-packagekit, rhnplugin
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
190 | Me <myuser> | 2011-03-22 08:42 | Install | 1
189 | Me <myuser> | 2011-03-22 08:37 | Erase | 1
188 | Me <myuser> | 2011-03-22 08:36 | Install | 1
187 | Me <myuser> | 2011-03-22 08:35 | Erase | 1
186 | Me <myuser> | 2011-03-22 08:31 | Install | 1
old transactions are assigned to the new user
Expected results:
something like
# yum history list
Loaded plugins: refresh-packagekit, rhnplugin
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
190 | Me <myuser> | 2011-03-22 08:42 | Install | 1
189 | REMOVED: <IlikeMyLongNam | 2011-03-22 08:37 | Erase | 1
188 | REMOVED: <IlikeMyLongNam | 2011-03-22 08:36 | Install | 1
187 | REMOVED: <IlikeMyLongNam | 2011-03-22 08:35 | Erase | 1
186 | REMOVED: <IlikeMyLongNam | 2011-03-22 08:31 | Install | 1
Comment 2RHEL Program Management
2011-05-26 22:44:38 UTC
Product Management has reviewed and declined this request. You may appeal this
decision by reopening this request.