From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
"Auto Update Errata" does not appear to be working properly for me.
Example: I have a system called "lucente" scheduled to receive updates to the
package "unzip-5.50-2", but the update is never applied.
VERSION: RHL 7.2
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Choose the Auto Update Errata for systems.
Not working for me either, but not quite the same scenerio (so I'm not sure if
it's the same bug?) I have 4 systems on 2 different accounts, all of them
have "auto errata update" checked, yet none of them do it when new errata are
released. I've let them go for almost a week to make sure, but they never
update themselves until I trigger it manually.
3 servers running RH9. Comments are the same as above - all set to auto
update, no updates actually occur. If you can tell me how, I can enable debug
logging and provide any additional data.
Mine not working either, two systems on RH7.3, if I manually schedule updates
they always go through but never get picked up automatically. Have left for
approx 7-10 days and they still don't get picked up.
up2date version: 2.8.40-3.7.3
RHN username: djluko
Systems affected: Luko.ORG, LifeFitness (three others are inactive)
I can confirm this on WE/ES/AS version 3 with update 4.2.5-1. I've
seen it work in the past but it doesn't always appear to.
How many of you guys are going through an RHN Proxy???
*** Bug 104630 has been marked as a duplicate of this bug. ***
*** Bug 110173 has been marked as a duplicate of this bug. ***
Please include a testplan when this moves to ON_QA. Thanks!
I don't believe this needs any testing by our QA group.
This is a www.redhat.com web site change only - the feature lists.
Please correct me if I'm wrong there.
All international Red Hat web sites (except Spain, which should be
done today) have been corrected to properly show Auto-Update as a
feature that requires the Management Module.
mass move to ON_QA for the QA push two days ago.
Scott, ok to move to PROD_READY per your additional comment #14, or
does this bug need to be given to another group as QA Contact per
debbie's additional comment #13?
All the changes have been made to the marketing pages on our
international web sites, so no need to pass this to another group - it