Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
If you delete any user who has previously created an activation key that still currently exists, the key(s) will be deleted as well.

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

How reproducible: 100%


Steps to Reproduce:
1. Create a test user of any name (I set role as admin)
2. Login to this user and create an activation key.
3. Logout of the test user, back in as another admin, and delete the user.
4. Check the activation key list.

Actual results:
Newly created activation key will now be gone.

Expected results:
Activation key should still exist.

Additional info:
This association appears to be inside of the foreman database, inside the katello_activation_key table. The 'user_id' column has the number of the user who created the activation key. If you set this id to any other user prior to deleting the one who currently owns the key, the key will continue to exist after user deletion.

Created redmine issue http://projects.theforeman.org/issues/12804 from this bug

Upstream bug component is Content Management

Moving to POST since upstream bug http://projects.theforeman.org/issues/12804 has been closed
-------------
Thomas McKay
Applied in changeset commit:katello|01e8b42104c8a5ff532273c52730b680fa34a4a6.

Executed the scenario as described in the initial description.  After deleting the user, observed that the activation key continues to exist as desired.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501