From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Description of problem:
After removing the sendmail rpm locally (was replaced by a qmail) and updating
the system's profile mit 'up2date -p' the previously shown erratas are not
longer shown as erratas in the system details on our satellite server.
I've reproduced this effect on two other systems. The result is attached as
screenshots. Also this test systems have sendmail and should see the sendmail
errata for example.
When I look for update with 'up2date -l' there is no difference. On the
satellite server I find the erratas under the outstanding package updates under
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. lookup the erratas of a system under system details
2. perform an up2date -p on the system
3. lookup up the erratas of a system under system details again
Actual Results: erratas are missing
Expected Results: same erratas as in 1.
Look's like some relations in the database are lost after an 'up2date -p'.
Created attachment 91473 [details]
Errata displayed before up2date -p
Created attachment 91474 [details]
Errata displayed after up2date -p
Created attachment 91475 [details]
Package list after up2date -p
Cristian, I'm a little bit confused. Let me ask a few questions:
1. Did you remove the sendmail package from system lnxc-329 before the first
attachment image was taken? And then ran the up2date -p?
2. Is the package list on the website for the system correct compared to the
results of rpm -qa ?
1. No. lnxc-329 does still have a sendmail package. On the first system where I
saw the problem I removed the sendmail packages, before I issued an 'up2date
-p'. After I noticed the errata problem, I verified it on two other machines.
One of those other machines was the lnxc-329.
2. At least the package count is identical (360 packages). Is there a way to
extract the packages list from the Satellite database to a text file? Then I
could make a diff.
The problem is solved although we're not 100% sure what the problem was. It
seems that the oracle database was the problem. After experiencing some
performance problems one of our database administrators checked the database and
noticed a long running checkpoint process. He also rebuilded the database
After that I checked the lnxc-329 profile and got it's errata displayed. Last
time I checked this was yesterday. So I not sure whether the restart or some
other process solved the errata problem.