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.

Bug 2222890

Summary: update event is not created after updating CV name
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Content ViewsAssignee: Samir Jha <sajha>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: medium Docs Contact:
Priority: high    
Version: 6.14.0CC: aruzicka, iballou, pcreech, sajha, sbible
Target Milestone: 6.14.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.10-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:19:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Ondrejka 2023-07-14 11:09:48 UTC
Description of problem:
When existing content view is updated, corresponding audit entry is not created

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

How reproducible:
always

Steps to Reproduce:
1. create a CV
2. update its name 
3. under Monitor > Audits search for 'type=katello/content_view and action=update'

Actual results:
no result

Expected results:
an update event should show up

Additional info:
Doesn't occur in 6.13
Found by QE automation: 
pytest tests/foreman/ui/test_audit.py -k  test_positive_update_event

The cv create event appears as expected

Comment 1 Adam Ruzicka 2023-07-17 12:34:02 UTC
Most likely caused by https://projects.theforeman.org/issues/36268 

@sajha Hi, is there a reason why cv name/label/description are excluded from being audited?

Comment 2 Samir Jha 2023-07-17 13:04:36 UTC
In 6.14, we use these update records to track changes that need publish. Name/label/description changes on a CV do not need a publish and hence are not audited. We can add it back and exclude those if needed.

Comment 3 Samir Jha 2023-08-01 17:45:24 UTC
Created redmine issue https://projects.theforeman.org/issues/36628 from this bug

Comment 4 Bryan Kearney 2023-08-02 20:03:20 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36628 has been resolved.

Comment 6 Sam Bible 2023-08-10 15:50:03 UTC
Verified on - 6.14 - Snap 11

Steps to Reproduce:
1. Create a CV
2. Update it's name and description

Actual results:
Update event for both shows up.

Expected results:
Update even for both shows up.

Comment 9 errata-xmlrpc 2023-11-08 14:19:56 UTC
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.14 security and bug fix update), 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-2023:6818