Red Hat Bugzilla – Bug 431321
Incorrect mails with check only when a repo is not accessible
Last modified: 2008-02-28 16:42:23 EST
yum.cron.daily treats all non-zero yum exit codes as equal in CHECK_ONLY
configurations. Today I got several mails from it like the below because the
EPEL mirror I use was not available (yeah, this is on EL but I think Fedora is
the upstream for yum-cron there so it'd be better to fix it in Fedora I think):
New updates available for host xxx:
Error: Cannot open/read repomd.xml file for repository: epel
Updates downloaded, use "yum -C update" manually to install them.
yum check-update is documented to return 0 if no updates are available, and 100
if there are updates available. yum.cron.daily should not treat all non-zero
exit codes as "updates are available" ones. I have mixed feelings about whether
it should even mail me if a repo was not available, but certainly not like it
currently does :)
Similar to the CHECK_FIRST solution presented in bug 429716. For CHECK_ONLY
setups, looks like this should always be done. Working on both bugs now.
yum-cron-0.8-1.fc7 has been submitted as an update for Fedora 7
yum-cron-0.8-1.fc8 has been submitted as an update for Fedora 8
yum-cron-0.8-1.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update yum-cron'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-1916
yum-cron-0.8-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
yum-cron-0.8-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.