If you are updating or obsoleting a package, it is not listed in yum's
transaction info as being removed, so it is not sent up to RHN as such. code
needs to be added to either check the ts info for packages that have a ts_state
of None, or to examine the transaction members for the updating and obsoleting
packates to see what they update and obsolete.
Originally discovered in comment #20 of bug 208850
Created attachment 155472 [details]
rhn yum plugin patch for dependency package support
i did not get the exact behavior when testing individual packages but i did see
that dependencies were not being updated correctly which might have caused this
behavior. i went ahead and added a fix, including the patch. can we retest with
this code change?
could you put in a test plan for this one.
basically you need to update a package using yum then check with the Web UI that
the package in the DB reflects what is on the local system.
1) yum update foo
2) go to rhn web ui
3) look at package list for system foobar
4) confirm system foobar package foo is same version as a rpm -q foo
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.