| Summary: | cgconfig fails to start if cgconfig.conf contains reference to an Active Directory user | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | paolo.larcheri |
| Component: | libcgroup | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | bsingharora, jsafrane, paolo.larcheri, pschiffe, varekova |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-05 07:21:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
ATTEMPT TO WORKAROUND: According to the man page SYSTEMD.SPECIAL(7): nss-lookup.target systemd automatically adds dependencies of type After for this target unit to all SysV init script service units with an LSB header referring to the $named facility. Therefore I tried to set the LSB header within the cgconfig sysV script as follows: ### BEGIN INIT INFO # Provides: cgconfig # Required-Start: $named # Required-Stop: # Should-Start: # Should-Stop: # Short-Description: Create and setup control group filesystem(s) # Description: Create and setup control group filesystem(s) ### END INIT INFO Then I rebooted but still cgconfig fails to start due to parsing errors, as if the expected order wasn't met: ---- Feb 23 09:53:37 pclarcheri2 cgconfig[898]: Starting cgconfig service: parsing failed at line number 23 Feb 23 09:53:37 pclarcheri2 cgconfig[898]: Loading configuration file /etc/cgconfig.conf failed Feb 23 09:53:37 pclarcheri2 cgconfig[898]: Failed to parse config file --- This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Hello, Paolo, is this issue still relevant? Based on how many people got interested in, it looks like it never was... :-) I have no longer been a fedora user for a while now, so I don't know if this bug still affects the distro. Anyway just close it, if I will be installing a fedora desktop somewhere, I will check if the bug is still there and possibly open a new one. Kind Regards, PL You are right :) Thanks for reply. |
Description of problem: Cgconfig fails to start if cgconfig.conf contains reference to an Active Directory user. This is due to the fact cgconfig.service does not Requires winbind.service to be started. Version-Release number of selected component (if applicable): systemd-37-3.fc16.i686 libcgroup-0.37.1-4.fc16.i686 samba-common-3.6.1-77.fc16.i686 samba-winbind-3.6.1-77.fc16.i686 Steps to Reproduce: 1. Put you F16 in an AD domain 2. Configure cgconfig to set any permissions for an AD user 3. Reboot the F16 box 4. # systemctl status cgconfig.service to check the service failed to start Additional info: cgconfig gets started by a sysv script, so there is no unit file where to specify the dependecy "cgconfig->winbind". Workaround: I usually workaround the problem by manually restarting cgconfig. Regards, Paolo Larcheri