Bug 520915
Summary: | cmirror init script should use killproc | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Nate Straz <nstraz> |
Component: | cmirror | Assignee: | Jonathan Earl Brassow <jbrassow> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | agk, ccaulfie, dwysocha, edamato, heinzm, jkortus, mbroz |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-30 09:05:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nate Straz
2009-09-02 20:21:55 UTC
Also check the lines regarding the kernel module removal. I can see this failing during our tests quite frequently because the module is not loaded. It should be checked if the module is loaded and then try to remove it. This also makes it possible to call the script twice with stop parameter and not fail. Ok, I'll try to fix these. However, reading the killproc man page, I'm not sure that it is appropriate. clogd will refuse to honor SIGTERM if there are still active cluster mirrors. Failing the SIGTERM, killproc will issue a SIGKILL - which we do not want... So, we want to wait for the SIGTERM to take effect, but not to issue the subsequent SIGKILL... rather, it should fail in that event. commit 6a5f12eea4e117b3ed50016e737fc4847ccbd634 Author: Jonathan Brassow <jbrassow> Date: Thu Dec 3 15:48:04 2009 -0600 cmirror: Fix-up init script behaviour (bug 520915) init script was throwing errors on 'stop' when it shouldn't have been. I have not run into this during recent RHEL 5.5 regression runs. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0307.html |