Bug 842487
Summary: | cobblerd fails to start (python can't find pam_start) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alan Crosswell <alan> |
Component: | cobbler | Assignee: | James C. <jimi> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | awood, cristian.ciupitu, ikke, jimi, ppinatti, scott, vanmeeuwen+fedora |
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: | 2013-08-01 01:14:29 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: | |
Embargoed: |
Description
Alan Crosswell
2012-07-24 01:46:06 UTC
Worked around with "setsebool -P httpd_can_network_connect_cobbler 1" Not sure whether this is supposed to be done by the cobbler RPM post-install script.... Unfortunately it's not a clear cut. The packaging guidelines don't mention anything explicit about SELinux, but you have to keep in mind that messing with the system configuration is controversial. Maybe the system administrator wants that boolean disabled and he will activate it only much later. On the other hand, maybe some basic stuff needed for start-up could be mentioned in a tiny document, e.g. README.Fedora (and README.(RH)EL). Right now http://cobbler.github.com/manuals/2.2.3/3/2_-_Installing_From_Packages.html doesn't mention too much. The SELinux tweak is indeed arguable, but the systemctl issue still remains. Adding the python interpreter in cobblerd.service (ExecStart=/usr/bin/python /usr/bin/cobblerd) seems to solve it. Could it be done so that cobbler can be started from systemctl again? Thanks I confirm it works if one adds python to sysctl script. The service not working without it definitely is a bug. cobbler-2.4.0-beta2.fc17.noarch cobbler-web-2.2.3-2.fc17.noarch You shouldn't have to mention the interpretor in the ExecStart field if the executable has the proper shebang. I know, that's weird. I didn't take time to investigate the reason. I wan't to get the first taste of cobbler before starting fixing anything. Just wanted to report back, since this bug is in new state. I could be changed to confirmed now. Hello, this issue has been opened for some time while we have a working fix. Can't we apply it so that users are able to start the cobbler service again in parallel to investigating the reason? Thanks! This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |