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?
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
Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.