Bug 1288005
| Summary: | systemctl can't read symlinks to SysVinit service scripts in /etc/init.d after upgrading to RHEL 7.2's systemd-219-19.el7 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.2 | CC: | akarlsso, andreas.kohn, bblaskov, chorn, hebron, jkurik, jscotka, lnykryn, martin.wilck, mnavrati, rainer.peter+redhat, redhat-bugzilla, robert.scheck, rsawhill, sderomedis, systemd-maint-list, systemd-maint, troels, vanhoof |
| Target Milestone: | rc | Keywords: | EasyFix, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-219-19.el7_2.3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, systemd ignored symbolic links in the /etc/rc.d/init.d/ directory. As a consequence, init scripts with symbolic links included in /etc/rc.d/init.d/ could not be started using systemd. With this update, systemd follows symbolic links included in /etc/rc.d/init.d/ to init scripts. Note that the real location of the init script must be on the partition that is mounted in the initial ramdisk (initrd).
|
Story Points: | --- |
| Clone Of: | 1285492 | Environment: | |
| Last Closed: | 2016-02-16 10:40:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1285492 | ||
| Bug Blocks: | 1289485 | ||
|
Description
Jan Kurik
2015-12-03 09:56:52 UTC
Cross-filed case #01566962 because we need this fix soon. When will the bug fix package be released publically? (In reply to Martin Wilck from comment #8) > When will the bug fix package be released publically? That is planned as part of bz1285492 for rhel7.3 and for 7.2.z here in this bz, can't say more on timeframe for the 7.2.z fix. 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-0199.html |