Bug 1382833
| Summary: | RHV-H 4.0 does not enable and automatically start the crond service | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Gordon Watson <gwatson> | |
| Component: | ovirt-node-ng | Assignee: | Ryan Barry <rbarry> | |
| Status: | CLOSED ERRATA | QA Contact: | jianwu <jiawu> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.0.3 | CC: | cshao, dfediuck, dguo, eheftman, huzhao, jiawu, knarra, leiwang, mgoldboi, mwest, obockows, qiyuan, rbarry, usurse, weiwang, yaniwang, ycui, yzhao | |
| Target Milestone: | ovirt-4.1.0-beta | Keywords: | Regression | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| 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: | ||||
| : | 1386135 (view as bug list) | Environment: | ||
| Last Closed: | 2017-04-20 18:59:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1386135 | |||
|
Description
Gordon Watson
2016-10-07 20:33:41 UTC
*** Bug 1383259 has been marked as a duplicate of this bug. *** An easy workaround is to use "systemctl enable crond". Hi yzhao, Could you reproduce this issue on QE env.? 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 *** Bug 1382600 has been marked as a duplicate of this bug. *** *** Bug 1387637 has been marked as a duplicate of this bug. *** 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.
Please ignore #c13 due to a typo. 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 |