| Summary: | chkconfig SERVICE returns wrong exit code and confuses puppet | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Florian <john> |
| Component: | chkconfig | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | mschmidt, notting, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | chkconfig-1.3.57-2.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-21 21:53:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Whoops, regression in the latest LSB fixes. Fixed by: http://git.fedorahosted.org/git/?p=chkconfig.git;a=commitdiff;h=3c9dcf4bf26658ebea02cc942ca1c859de8efcc4 Will get pushed out in an update in the near future. chkconfig-1.3.57-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/chkconfig-1.3.57-2.fc16 (In reply to comment #1) > Whoops, regression in the latest LSB fixes. Fixed by: > http://git.fedorahosted.org/git/?p=chkconfig.git;a=commitdiff;h=3c9dcf4bf26658ebea02cc942ca1c859de8efcc4 > > Will get pushed out in an update in the near future. The fix worked great, as I noted in bhodi. Bill, I'm curious about the QA process used in Fedora. We had this same failure when systemd was first introduced, although that was triggered by systemd being broken (at the time) with it's implementation of 'systemctl is-enabled ...' I often, but not always, see mentions of autoqa (or something like that) here in BZ. Do unit tests get written for for such cases that help autoqa? Are those tests in an independent package or are they part of each project and held only in the SCM? I ask because I wouldn't mind helping out when I can to make any such tests better, but really don't know that side of the Fedora infrastructure. Any pointers on how to become a better contributor would be appreciated. (In reply to comment #3) > Bill, I'm curious about the QA process used in Fedora. We had this same > failure when systemd was first introduced, although that was triggered by > systemd being broken (at the time) with it's implementation of 'systemctl > is-enabled ...' I often, but not always, see mentions of autoqa (or something > like that) here in BZ. Do unit tests get written for for such cases that help > autoqa? Are those tests in an independent package or are they part of each > project and held only in the SCM? autoqa is currently only handling generic tests (dependency checks, upgrade path checks, and so on.) It's intended to at some point in the future support package-specific unit tests, but it's not there yet. In this case, I ran a whole bunch of tests on the LSB and related support (including the LSB init script test suite), but didn't check the basic case you mentioned before releasing, so it's on me. Package chkconfig-1.3.57-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing chkconfig-1.3.57-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0685/chkconfig-1.3.57-2.fc16 then log in and leave karma (feedback). (In reply to comment #3) > I ask because I wouldn't mind helping out when I can to make any such tests > better, but really don't know that side of the Fedora infrastructure. Any > pointers on how to become a better contributor would be appreciated. John, if you're interested in contributing to Fedora QA, these wiki pages should be good starting points: http://fedoraproject.org/wiki/AutoQA http://fedoraproject.org/wiki/QA chkconfig-1.3.57-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: According to the man page, one should be able to execute 'chkconfig SERVICE' and examine the exit code to determine if a service is enabled to start (or not) at boot. This no longer works, it appears that the service is always disabled now. This makes a complete mess out of puppet which uses this technique to discover the current state. Version-Release number of selected component (if applicable): chkconfig-1.3.57-1.fc16 How reproducible: always Steps to Reproduce: $ sudo chkconfig yum-cron off $ sudo chkconfig yum-cron; echo $? 1 $ sudo chkconfig yum-cron on $ sudo chkconfig yum-cron; echo $? 1 Expected results: The exit code in the 2nd query above should return 0, not 1. Additional info: From the man page: When chkconfig is run with only a service name, it checks to see if the service is configured to be started in the current runlevel. If it is, chkconfig returns true; otherwise it returns false.