Bug 684633

Summary: Service are started in the same process group as clurgmgrd
Product: Red Hat Enterprise Linux 5 Reporter: Brad Hubbard <bhubbard>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED WONTFIX QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5CC: bhubbard, cluster-maint, rmitchel
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-29 17:25:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Test case
none
Fix none

Description Brad Hubbard 2011-03-14 01:26:19 UTC 
Description of problem:
When clurgmgrd launches a service it forks and calls execle. this creates a new process in the same process group. If the new process issues a signal to the process group such as kill(0, SIGTERM) then the entire process group responds including clurgmgrd.

Version-Release number of selected component (if applicable):
rgmanager-2.0.52-9

How reproducible:
Consistently

Steps to Reproduce:
1. Create a service that uses the kill(0, SIGTERM) and start it.
2.
3.
  
Actual results:
clurgmgrd receives SIGTERM


Expected results:
clurgmgrd should not shut down

Additional info:
Comment 2 Lon Hohberger 2011-04-18 19:23:59 UTC 
Created attachment 492988 [details]
Test case

This unit test can be attached as a script to a service.  Place this service script on all nodes and simply create a service which looks like the following:

  <service name="test">
    <script name="pgtest" file="/root/pgtest.sh" />
  </service>

Ensure you have gcc installed on all hosts, as the script compiles a quick bit of C code to run.

If run on a version of rgmanager exhibiting this problem (child processes in the same process group), the script will refuse to start and log an error in the system logs.

On a system without the process group problem, the script will start without issue.  Running this test script from rgmanager is likely to require SELinux being disabled or at least placed in permissive mode.
Comment 3 Lon Hohberger 2011-04-18 19:26:28 UTC 
Created attachment 492989 [details]
Fix
Comment 7 RHEL Program Management 2011-07-29 17:25:13 UTC 
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.