Description of problem: rhn_check does not see a new version of the package and exits. This occurs when updates are scheduled from Software->Errata and also seems to prevent autoupdates from occuring. However, when an update is scheduled via Software->Packages->Upgrade it does work. Version-Release number of selected component (if applicable): System is RHEL v.5 Server i386, registered to rhn.redhat.com How reproducible: For me, it's happening very consistently. Steps to Reproduce: 1. Install an out-of-date package from CD, e.g. squid-2.6.STABLE6-3.el5 2. run rhn_register Actual results: rhn_check exits silently, however the rhn interface will report that while the sheduled event has occurred, the errata has still not been patched Expected results: The scheduled event should occur, and the errata patch should be applied. Additional info: yum update works fine. Also, if the update to the package is scheduled using a different method (i.e. not via errata) it will work.
I can confirm the exact same problem is happening to me.
I'm confused here. Bug is reported on RHEL4, but comment #0 talks about RHEL5. Also I have tested this on RHEL4 and it worked as expected (RHEL4@s390x - Errata.stage): # rpm -ivh /mnt/redhat/released/RHEL-4/U3/AS/s390x/tree/RedHat/RPMS/squid-2.5.STABLE6-3.4E.12.s390x.rpm Preparing... ########################################### [100%] 1:squid ########################################### [100%] # up2date -p Updating package profile... Updating transaction history... Now scheduled errata update on Software -> Errata on WebUI. # rhn_check Name Version Rel Arch ---------------------------------------------------------------------------------------- squid 2.5.STABLE14 1.4E.el4_6.1 s390x squid-2.5.STABLE14-1.4E.el4 ########################## Done. Preparing ########################################### [100%] Installing... 1:squid ########################################### [100%] # rpm -q squid squid-2.5.STABLE14-1.4E.el4_6.1.s390x So what exactly will be fixed here?
Hello, asking publicly so anybody can answer.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.