Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 517861

Summary: recovery policy "restart" doesn't work
Product: Red Hat Enterprise Linux 5 Reporter: Masatake YAMATO <yamato>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: cluster-maint, edamato
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: 2009-08-21 20:58:12 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:
Attachments:
Description Flags
experimental patch to fix the bug none

Description Masatake YAMATO 2009-08-17 14:47:29 UTC 
Description of problem:

Even though restart is specified to recovery policy in a service, the servie is relocated.
About cluster.conf see the attachment.


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

rgmanager-2.0.46-1.3.

How reproducible:

The service is httpd. Stopping the httpd with service command.

Steps to Reproduce:
1. Deploy cluster with attach cluster.conf
2. Do service httpd stop at host where the httpd run.
3.
  
Actual results:

The service migrate to another cluster node without any trying to restart.

Expected results:

Restart httpd again at the node where it has run.

Additional info:

After applying the attached patch, the restart policy works as expected.
Comment 1 Masatake YAMATO 2009-08-17 14:52:00 UTC 
Created attachment 357660 [details]
experimental patch to fix the bug
Comment 2 Lon Hohberger 2009-08-21 20:58:12 UTC 

*** This bug has been marked as a duplicate of bug 449394 ***