| Summary: | [z-stream clone - 4.0.4] RHV-H 4.0 does not enable and automatically start the crond service | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-node-ng | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0.3 | CC: | cshao, dfediuck, dguo, fdeutsch, huzhao, jiawu, leiwang, mgoldboi, mwest, qiyuan, rbarry, trichard, usurse, weiwang, yaniwang, ycui, yzhao |
| Target Milestone: | ovirt-4.0.4-1 | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, crond was not enabled in the default configuration of RHVH 4. Due to the absence of cron, logrotate did not trigger, possibly resulting in very large log files which would fill the disk. With this release, cron is now enabled by default, so logrotate runs normally.
|
Story Points: | --- |
| Clone Of: | 1382833 | Environment: | |
| Last Closed: | 2016-10-31 08:58:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1382833 | ||
| Bug Blocks: | |||
Cancel ping. We can verify this bug according Target Milestone. So Verify this bug according #c1. 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-2016-2125.html |
Test version: redhat-virtualization-host-4.0-20161012.0 imgbased-0.8.5-0.1.el7ev.noarch Test result: The default status of crond server is enable. So the bug is fixed. # systemctl status crond ● crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-10-18 10:55:45 CST; 7h ago Main PID: 1716 (crond) CGroup: /system.slice/crond.service └─1716 /usr/sbin/crond -n Hi Ryan, Could you help to fill the "Fixed in version" area? Thanks.