Bug 1326892

Summary: Systemd suddenly not understanding symlinks in /etc/init.d
Product: [Fedora] Fedora Reporter: dag
Component: systemdAssignee: systemd-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:25:26 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:

Description dag 2016-04-13 16:44:30 UTC
Description of problem:
The sysv init.d emulation in systemd is not able to start up products in /etc/init.d that are symlinked 

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

How reproducible:
Always

Steps to Reproduce:
1.Create symlink in /etc/init.d to original initscript.Like many legacy products still do...
2.Enable it with systemctl enable <script>
3.Run it with systemctl start <script>

Actual results:
You get: "Failed to start <script>.service: Unit <script>.service failed to load: No such file or directory.

Expected results:
The service would start up

Additional info:

Comment 1 Fedora End Of Life 2016-07-19 19:25:26 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.