Scenario:

System has not checked into RHN in a while. An errata is released that applies
to it. A week later, the errata has not been applied (of course, the system has
not checked in) but auto-errata update has scheduled the errata application.

Here is how various pages in the webui reflect this scenario currently (RHN 500):

- /rhn/errata/details/SystemsAffected.do? ('Affected Systems' tab for the errata)
  says 'no systems'

- /network/systems/details/history/pending.pxt ('Events > Pending' tab for the
SDC of the system)
  lists 'errata update scheduled by (none)' <= for the errata. scheduled on the
same day the errata was released.

- /rhn/systems/details/ErrataList.do ('Software > Errata' tab for the SDC of the
system)
  does *not* list the errata in question. Lists other erratas though, with the
clock icon to indicate they are pending. However, today is 3/14, the errata in
our example was released 3/8, the most recent errata listed on this page is 1/11

- /rhn/systems/details/packages/UpgradeablePackages.do ('Software > Packages >
Upgrade' tab for SDC) 
  just to verify, errata does not show up on this list. errata is for evolution
and no evolution upgrades are listed here.

- /rhn/errata/AllErrata.do (all errata page)
  errata is shown on this screen, but the 'systems' column says there are 0
systems that it applicable to. How about our system that has it pending? perhaps
the column should list pending and still applicable?

- /network/systems/details/history/event.pxt ('events > pending' tab in sdc)
  shows the errata is scheduled / queued and not yet picked up by system

Note that the errata in question was released pre-RHN500.