Bug 150344

Summary: Relocate to node already running a service improperly fails
Product: [Retired] Red Hat Cluster Suite Reporter: Derek Anderson <danderso>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED RAWHIDE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
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: 2005-05-06 20:43:38 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 Derek Anderson 2005-03-04 19:05:24 UTC
Description of problem:
Service FOO is already running on node link-10.  Tell it to relocate
to link-10.  It correctly stops then restarts the service on link-10,
then reports failure.  My expectation is that this is considered success.

[root@link-08 ~]# clusvcadm -r FOO -m link-10
Trying to relocate FOO to link-10...failed
[root@link-08 ~]# echo $?
255

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lon Hohberger 2005-03-04 19:11:20 UTC
Correct, relocate service foo to node bar should be treated as a
"restart" operation.

Comment 2 Lon Hohberger 2005-03-21 21:07:35 UTC
Fixed in CVS