Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
whenever a user tries to clone an existing role with many filters, many audit records are created.
- a single record for Role create
- and a record for Role update for each filter in the original role
Version-Release number of selected component (if applicable):
6.5.0-2
Steps to Reproduce:
1. take e.g. a viewer role
2. clone it
3. see audit logs
Actual results:
many audit logs for a simple action
Expected results:
perhaps recognizing the "clone" action would be nice, or aggregating the individual updates into a single one.
Created attachment 1508291[details]
screenshot of the uadit page
this screenshot shows the audit page after cloning a manager role (the audit record at the bottom). since the original role had many filters attached to it, these have been added one by one to the newly created clone as well and each operation generated a standalone audit record.
there are actually 2 full pages of such records.
- could they be aggregated into a single record?
After the discussion with mhulan and kavita we came to conclusion that the solution would be to incorporate the corresponding htt prequest in the audit and make the audits searchable by it, so user can filter/filter out the audits belonging to the same user action.
- changing the title and also the target milestone to sat6.6.0
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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366