Bug 724888

Summary: error in /etc/cron.daily/0yum.cron script, CHECK_ONLY=yes doesn't work
Product: Red Hat Enterprise Linux 6 Reporter: Pavel Lisý <pavel.lisy>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: ahabig, james.antill, pknirsch
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-06 15:58:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavel Lisý 2011-07-22 07:49:16 UTC 
Description of problem:
There is error in script which cause disfunction of settings in /etc/sysconfig/yum-cron

Version-Release number of selected component (if applicable):
yum-cron-0.9.2-2.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. set CHECK_ONLY=yes in /etc/sysconfig/yum-cron
2. system is updated every night instead of check only
3.
  
Actual results:
with this setting: CHECK_ONLY=yes
system is checked for update every night, sends mail info and then is updated

Expected results:
with this setting: CHECK_ONLY=yes
system is checked for update every night and sends mail info only

Additional info:
change line 15 in /etc/cron.daily/0yum.cron
from:
  source /etc/sysconfig/yum-cron
to:
  . /etc/sysconfig/yum-cron
Comment 1 James Antill 2011-07-22 14:07:23 UTC 
 According to the bash man page "source" and "." are synonyms.
 Are you sure that is the only thing you changed to go from working to not-working?
Comment 3 Pavel Lisý 2011-09-06 13:21:59 UTC 
It was my fault, there was another process making updates (in rpm package yum-autoupdate) and than I couldn't find this bugzilla record to cansel it. Sorry.
Comment 4 Pavel Lisý 2011-09-06 13:22:57 UTC 
You should close this "bug". Thanks.