Description of problem:
not long after the upgrade to 5.0.1 in hosted today, a customer received 107
errata emails about the rhn-yum-plugin erratum that was released today
funny thing is that 107 systems are listed as being affected in the system
summary in the email. 107 systems listed in 107 emails. each list of systems is
the same across emails.
similarly another customer under the same org received 8 emails for the 8
systems that were affected by the same erratum.
I will attach one of the emails with full headers from the 107-email erratum
deluge mentioned above in a private comment.
note: each email is sent to the same login, each email is re: the same erratum,
and each email contains the same systems in the affected systems list.
Customer reports other accounts that received similar dupe errata emails, only
of the rhn-yum-plugin erratum.
customer reports rhn-yum-plugin erratum is the only one they've received emails
for. other applicable errata have been released yet no emails received on them.
as of ~3pm eastern today, the rhn-yum-errata plugin alert was resent (only one
email!) plus alerts for other errata as well. attaching a copy of one of this
batch of more correct emails.
Created attachment 154953 [details]
email that was sent out today, only one copy per errata of this batch was received
The first attachment is from taskomatic from a task that was inadvertantly
re-enabled by a production push (RHN 501 hosted). The second attachment
includes a similarly worded email that is sent out by a python script that is
run by production operations and produces the correct output.
I worked with production operations to disable the task that was erroneously
sending out multiple emails (5-17-2007) and have turned that off in the
configuration files so it doesn't inadvertantly get re-enabled during the next
Closing as CURRENTRELEASE.
disassociating CLOSED bugs