Bug 2055410

Summary: Sync Summary Report Incorrectly Lists All Erratas Instead of Just Newly Synced Erratas
Product: Red Hat Satellite Reporter: myoder
Component: EmailAssignee: Lukas Zapletal <lzap>
Status: CLOSED DUPLICATE QA Contact: Shweta Singh <shwsingh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: afeferku, ahumbe, apatel, arsingh, mhulan
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-19 15:56:58 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 myoder 2022-02-16 20:40:16 UTC 
Description of problem:

Configured admin user to subscribe to the "Sync errata" email notifications.  Then I synced the RHEL7 Server repository.  There was only 1 rpm and 1 errata installed as seen from the Content => Sync Status page, as well as by the "Actions::Katello::Repository::IndexContent" task from the dynflow console:

new_content:
  rpm: 1
  erratum: 1


Yet the email sent to my admin user shows it synced these errata counts/types:

 207 Security
 358 Bugfix
 67  Enhancement

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

How reproducible:
always

Steps to Reproduce:
1. Have a RHEL 7 repository fully synced.  
2. Configure a user to subscribe to "Sync errata" email notifiication.
2. Wait for a new errata to be released for repository.
3. Sync the repository.

Actual results:
The email includes a lot more erratas than were actually synced.

Expected results:
Expect the email to only include the erratas that were synced.

Additional info:
Seems like a regression since this was working correctly in Satellite 6.9.
Comment 3 myoder 2022-07-19 15:56:58 UTC 

*** This bug has been marked as a duplicate of bug 2044314 ***
Comment 4 Red Hat Bugzilla 2023-09-15 01:51:59 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days