Description of problem: Jenkins fails to start when installed on a freshly installed VM with nothing on it. Apr 21 11:57:58 jenkins systemd[1]: Starting Jenkins continuous build server... -- Subject: A start job for unit jenkins.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit jenkins.service has begun execution. -- -- The job identifier is 7725. Apr 21 11:57:58 jenkins jenkins[22594]: /usr/libexec/jenkins/jenkins: line 45: /etc/init.d/functions: No such file or directory Apr 21 11:57:58 jenkins systemd[1]: jenkins.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit jenkins.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. This appears to indicate that Jenkins is packaged with a SysV-reliant script that is not going to work on Fedora, since there is no package that provides /etc/init.d/functions. Version-Release number of selected component (if applicable): 1.651.3 How reproducible: Completely. Steps to Reproduce: 1. Install Fedora 30 (used netinstall iso) 2. dnf install jenkins 3. systemctl start jenkins Actual results: Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. Expected results: Jenkins should start Additional info:
Okay, mystery solved! jenkins is missing a dependency on initscripts This problem can be reproduced if you use netinstall, go with the default package selection, and then install jenkins on top of that. Apparently enough things depend on initscripts that almost any fuller-featured system is going to work fine. Also, 'dnf provides' fails to find the file's provider by its exact path, which is what caused me to initially believe the wrong init script got packaged: # dnf provides '/etc/init.d/functions' Error: No Matches found [root@gadget-xps images]# dnf provides '*/etc/init.d/functions' Error: No Matches found # dnf provides '*/init.d/functions' initscripts-10.01-2.fc30.x86_64 : Basic support for legacy System V init scripts Repo : @System Matched from: Filename : /etc/rc.d/init.d/functions initscripts-10.01-2.fc30.x86_64 : Basic support for legacy System V init scripts Repo : fedora Matched from: Filename : /etc/rc.d/init.d/functions Somehow only /etc/rc.d/init.d/functions is present on the package: # rpm -ql initscripts | grep functions /etc/rc.d/init.d/functions Even though /etc/init.d/functions does point to initscripts when installed: # rpm -qf /etc/init.d/functions initscripts-10.01-2.fc30.x86_64
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.