Bug 429867

Summary: daily summary email shows incorrect listing of queued/failed/completed
Product: [Retired] Red Hat Network Reporter: daryl herzmann <akrherz>
Component: RHN/OtherAssignee: Mike Orazi <morazi>
Status: CLOSED CURRENTRELEASE QA Contact: Amy Owens <aowens>
Severity: low Docs Contact:
Priority: low    
Version: rhn500CC: rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: US=16959
Fixed In Version: 5.0.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-26 20:22:02 UTC Type: ---
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: 444753, 444756, 444757, 444761, 444834    
Bug Blocks: 431812, 443075    
Attachments:
Description Flags
RHN Status Email for 10 Jan 2008
none
RHN Status Email for 24 Jan 2008
none
RHN Status Email for 25 Jan 2008
none
RHN Status Email for 26 Jan 2008
none
RHN Status Email for 29 Jan 2008
none
RHN Status Email for 1 Feb 2008
none
RHN Status Email for 2 Feb 2008
none
RHN Status Email for 8 Feb 2008
none
RHN Status Email for 9 Feb 2008
none
RHN Status Email for 14 Feb 2008
none
RHN Status Email for 29 Feb 2008
none
RHN Status Email for 11 Mar 2008
none
RHN Status Email for 14 Mar 2008
none
RHN Status Email for 9 Apr 2008 none

Description daryl herzmann 2008-01-23 15:33:14 UTC
Lately, it seems that the daily rhn summary email only contains a listing
of errata that was queued.  I can't remember seeing anything failing or
actually completed, while on rhn hosted webUI I can see plenty of failed
and completed actions.

The attached email illustrates this only showing queued actions.

Comment 1 daryl herzmann 2008-01-23 15:33:14 UTC
Created attachment 292653 [details]
RHN Status Email for 10 Jan 2008

Comment 2 daryl herzmann 2008-01-24 16:34:35 UTC
Created attachment 292810 [details]
RHN Status Email for 24 Jan 2008

Another example showing the issue of only reporting queued errata.

Comment 3 daryl herzmann 2008-01-25 15:42:58 UTC
Created attachment 292951 [details]
RHN Status Email for 25 Jan 2008

Weird, today's email doesn't have a "Queued" column and has completed actions,
but those numbers are way too low.

Comment 4 daryl herzmann 2008-01-26 13:54:12 UTC
Created attachment 293048 [details]
RHN Status Email for 26 Jan 2008

The Queued column is back, but still is not correct.  All of those 2007 errata
were not queued, but actually completed on a machine that checked in for the
first time this year...

Comment 5 daryl herzmann 2008-01-29 15:27:07 UTC
Created attachment 293289 [details]
RHN Status Email for 29 Jan 2008

Today's RHN status email is getting closer! :)

This time there are 5 errata listed under Synopses, but only 4 in the Errata
Update.  The yum-rhn-plugin is missing from the first list.

Comment 6 daryl herzmann 2008-02-01 16:27:21 UTC
Created attachment 293745 [details]
RHN Status Email for 1 Feb 2008

Only queued numbers are shown, which appear to be correct, but it is hard to
tell with two RHSA-2008:0055 listed.  The problem is that a good number should
have shown up as completed.

Comment 7 daryl herzmann 2008-02-03 15:38:17 UTC
Created attachment 293835 [details]
RHN Status Email for 2 Feb 2008

This status email only shows queued actions.  The day prior to this email, I
manually installed lots of errata and errata like the autofs and kernel errata
were successfully installed on many machines besides 0.

Comment 9 daryl herzmann 2008-02-08 14:45:47 UTC
Created attachment 294362 [details]
RHN Status Email for 8 Feb 2008

Status email showing more queued events for RHSA-2008:0103 than I have systems
(113).	Also, only queued events are shown.  There were a bunch of failed and
completed actions not shown.

Comment 10 daryl herzmann 2008-02-10 01:37:08 UTC
Created attachment 294482 [details]
RHN Status Email for 9 Feb 2008

Today's RHN status email showing 'RHBA-2008:0102' listed under synopsis, but no
events listed above.  Also, the completed column is out of alignment for some
reason.

Comment 12 daryl herzmann 2008-02-14 14:40:48 UTC
Created attachment 294912 [details]
RHN Status Email for 14 Feb 2008

Email only shows completed actions this time?

For some reason, it shows 44 completed actions for RHEA-2008:0086 , which is
not close to correct.  Should be 3, I think.

Comment 14 daryl herzmann 2008-02-29 18:01:15 UTC
Created attachment 296391 [details]
RHN Status Email for 29 Feb 2008

This one shows 155 queued for RHSA-2008:0146, I only have 116 systems.

Comment 15 daryl herzmann 2008-03-11 13:29:12 UTC
Created attachment 297611 [details]
RHN Status Email for 11 Mar 2008

Only queued events shown and 160 tzdata (way more than machines I have)

Comment 17 daryl herzmann 2008-03-14 13:40:33 UTC
Created attachment 298047 [details]
RHN Status Email for 14 Mar 2008

Example showing 1 errata listed under "Synopses" but nothing under "Update"

Comment 21 daryl herzmann 2008-04-09 13:24:30 UTC
Created attachment 301801 [details]
RHN Status Email for 9 Apr 2008

Showing 145 queued actions for the squid errata.  I don't have that many
machines.

Comment 22 Mike Orazi 2008-04-10 03:22:02 UTC
So far in this investigation, I think there are a handful of issues being reported:

1.  There are formatting issues with the email, causing numbers to not line up
under the appropriate field in the report.  This is causing
confusion/inconsistency with the data that is reflected in the web application.

NOTES:  Work in progress.

2.  There are inconsistencies between the Errata Update & Errata Synopsis
section of the email.

NOTES:  Working to identify the root cause.

3.  The report suggests that there are more actions than servers in some cases.

NOTES:  For each reported instance, the erratum in question had been pushed
multiple times within a 24 hour period, which resulted in multiple actions
scheduled to update the erratum in question.  The report is technically correct
in each of the cases mentioned, but obviously misleading.

4.  Comment #12 is reporting vastly larger than expected number.

NOTES:  Working to identify the root cause.