Bug 1204175

Summary:	cronie-anacron-1.4.4-14.el6.x86_64 doesn't like its own /etc/anacrontab syntax
Product:	Red Hat Enterprise Linux 6	Reporter:	John T. Rose <inode0>
Component:	cronie	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	high	Docs Contact:
Priority:	high
Version:	6.6	CC:	jprokes, psklenar, rhack, salmy, tlavigne, tmraz
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cronie-1.4.4-15.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-30 08:09:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John T. Rose 2015-03-20 14:16:34 UTC

Description of problem:

After updating from cronie-anacron-1.4.4-12.el6.x86_64 to cronie-anacron-1.4.4-14.el6.x86_64 anacron is unhappy with /etc/anacrontab.

# rpm -q cronie-anacron
cronie-anacron-1.4.4-12.el6.x86_64
# rpm -V cronie-anacron
# anacron -T
#

# rpm -q cronie-anacron
cronie-anacron-1.4.4-14.el6.x86_64
# rpm -V cronie-anacron
# anacron -T
anacron: Invalid syntax in /etc/anacrontab on line 5 - skipping this line
anacron: Invalid syntax in /etc/anacrontab on line 6 - skipping this line
anacron: Invalid syntax in /etc/anacrontab on line 7 - skipping this line

It seems unhappy about the stock variable declarations

SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

Version-Release number of selected component (if applicable):

cronie-anacron-1.4.4-14.el6.x86_64

How reproducible:

Always so far as I know now.

Steps to Reproduce:
1. Upgrade cronie-anacron to version 1.4.4-14
2. Run anacron -T or most anything else
3. See invalid syntax messages

Actual results:


Expected results:


Additional info:

Comment 3 Tomas Mraz 2015-03-20 14:53:40 UTC

This is serious regression and I am sorry for that.

Comment 17 errata-xmlrpc 2015-03-30 08:09:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0754.html