Bug 913032

Summary:	Spacewalk keeps sending out errata notifications after each reposync
Product:	[Community] Spacewalk	Reporter:	Jan Pazdziora <jpazdziora>
Component:	Server	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.8	CC:	jdobes, jpazdziora, tkasparek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-java-1.10.91	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-02 13:14:44 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:
Bug Depends On:
Bug Blocks:	991452

Description Jan Pazdziora 2013-02-20 09:18:45 UTC

Description of problem:

As described at https://www.redhat.com/archives/spacewalk-list/2012-November/msg00186.html

Spacewalk 1.8 server with synces EPEL5 repositories. After each sync, Spacewalk sends out the same errata notifications for updates on some of our clients.

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

1.8

How reproducible:

Deterministic.

Steps to Reproduce:
1. Create channel and repository which has updateinfo (erratas).
2. Have some client registered which is not completely up-to-date.
3. Run spacewalk-repo-sync.
  
Actual results:

Errata notifications are sent after each spacewalk-repo-sync.

Expected results:

Errata notifications are sent only after the first time spacewalk-repo-sync gets the errata.

Additional info:

Presumably, we reset the modified/last_modified upon every spacewalk-repo-sync. Could we use something like issue date of the errata?

Comment 2 Jan Dobes 2013-06-11 10:15:27 UTC

I was unable to reproduce this with these steps. But I noticed unnecessary emails with repo-syncing channels even without systems, with same packages architecture or not. Errata notifications are represented basically as errata-channel relation and they were all recreated for example after repo-sync of blank channel. Now are notifications generated only first time and will not be recreated.

spacewalk.git: 178fe375889d714781f61e08fc7f837db5978f5a

Comment 3 Tomáš Kašpárek 2013-08-02 13:14:44 UTC

Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.