Bug 1382833 – RHV-H 4.0 does not enable and automatically start the crond service

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1382833 - RHV-H 4.0 does not enable and automatically start the crond service

Summary:	RHV-H 4.0 does not enable and automatically start the crond service

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-node-ng (Show other bugs)
Sub Component:
Version:	4.0.3
Hardware:	Unspecified Linux

Priority	high Severity urgent
Target Milestone:	ovirt-4.1.0-beta
Target Release:	---
Assigned To:	Ryan Barry
QA Contact:	jianwu
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Duplicates:	1382600 1383259 1387637 (view as bug list)
Depends On:
Blocks:	1386135
	Show dependency tree / graph

Reported:	2016-10-07 16:33 EDT by Gordon Watson
Modified:	2017-08-07 22:36 EDT (History)
CC List:	19 users (show)

See Also:
Fixed In Version:	redhat-release-virtualization-host-4.0-5.1.el7
Doc Type:	Bug Fix
Doc Text:	Previously, the crond service was not enabled in the default configuration of Red Hat Virtualization Host (RHVH) 4.x. As a result, the log rotation functionality was not triggered, resulting in very large log files which could potentially fill the disk. In this release, the bug was fixed. As a result, the crond service is now enabled in the default configuration and log rotation functions as required.
Story Points:	---
Clone Of:
Clones:	1386135 (view as bug list)
Environment:
Last Closed:	2017-04-20 14:59:58 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	2690541	None	None	None	2016-10-10 11:57 EDT
Red Hat Product Errata	RHEA-2017:1114	normal	SHIPPED_LIVE	redhat-virtualization-host bug fix and enhancement update	2017-04-20 18:57:46 EDT

Groups: None (edit)

Description Gordon Watson 2016-10-07 16:33:41 EDT

Description of problem:

RHV-H 4.0 does not have 'crond' enabled, and so it does not start automatically. The result of this is that 'logrotate' doesn't run and files such as 'vdsm.log' and '/var/log/messages' just grow and grow, potentially filling up '/var'.

This is a regression of functionality from RHEV-H 3.6, in which 'crond' was started automatically.


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

RVH_4.0 20160919.0.el7


How reproducible:

100%.


Steps to Reproduce:

1. Run 'ps -ef | grep cron'.
2. Run 'systemctl status crond.service'.
3. Observe '/var/log/vdsm' and see only one (large) vdsm log file.


Actual results:

No log rotation.


Expected results:

Log rotation.


Additional info:

Comment 4 Yaniv Kaul 2016-10-10 09:25:11 EDT

*** Bug 1383259 has been marked as a duplicate of this bug. ***

Comment 5 Fabian Deutsch 2016-10-10 15:52:59 EDT

An easy workaround is to use "systemctl enable crond".

Comment 7 cshao 2016-10-10 22:36:22 EDT

Hi yzhao,

Could you reproduce this issue on QE env.?

Comment 8 Yihui Zhao 2016-10-10 23:42:22 EDT

Hi,all
   i reproduce the bug on rhvh-4.0-0.20160919.0+1.

Here is my steps:
#1.install RHVH4.0-0.20160919
#2.Run 'ps -ef | grep cron'.
#3.Run 'systemctl status crond.service'.
#4.add host to engine




Result:
1.crond service inactive
2.Before add host to engine,the vdsm.log is  empty,but after add host to engine,
such as  "vdsm.log" just grow and grow.

Thanks,
Yihui

Comment 9 Dan Kenigsberg 2016-10-11 05:38:09 EDT

*** Bug 1382600 has been marked as a duplicate of this bug. ***

Comment 12 Ryan Barry 2016-10-24 05:18:56 EDT

*** Bug 1387637 has been marked as a duplicate of this bug. ***

Comment 14 jianwu 2017-01-17 01:44:41 EST

Hi, all 

I have verified this bug on redhat-virtualization-host-4.1-20170116.0 as follows:

Test version:
redhat-virtualization-host-4.1-0.20170116.0

#1.Install RHVH new build
#2.Run 'ps -ef | grep cron'
#3.Run 'systemctl status crond.service'
#4.add host to engine

Actual Results
1. After step 2, # ps -ef|grep cron
root      1402     1  0 14:08 ?        00:00:00 /usr/sbin/crond -n
root     21870 20370  0 14:28 pts/0    00:00:00 grep --color=auto cron
2. After step 3, # systemctl status crond.service
● crond.service - Command Scheduler
   Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2017-01-17 14:08:24 CST; 21min ago
 Main PID: 1402 (crond)
   CGroup: /system.slice/crond.service
           └─1402 /usr/sbin/crond -n
3. After step 4, "vdsm.log" just grow normally

So I think this bug is fixed in this version. I will change status to Verified.

Comment 15 cshao 2017-01-17 01:47:07 EST

Please ignore #c13 due to a typo.

Comment 16 errata-xmlrpc 2017-04-20 14:59:58 EDT

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://access.redhat.com/errata/RHEA-2017:1114

Note You need to log in before you can comment on or make changes to this bug.