[Cluster-devel] Small Bug in follow-service.sl

[Cluster-devel] Small Bug in follow-service.sl

[Marc Grimme]

Hello,
a few weeks ago I stumbled over an issue in the follow-service functionality in rgmanager event scripting with rind.

When I wrote it I didn't think about people not having a specifically configured failover domain.

But I had to setup the follow-service with a default failover domain (no failover domain configured defaults to all hosts being in the failover domain). In this case the follow-service would not work an did not start the service when a node down event was triggered.

Attached you'll find the follow-service script that has this issue fixed and a patch against the latest stable RHEL6 GIT of cluster3.

Regards
Marc.

______________________________________________________________________________

Marc Grimme

E-Mail: grimme at atix.de

ATIX Informationstechnologie und Consulting AG | Einsteinstrasse 10 |
85716 Unterschleissheim | www.atix.de

Enterprise Linux einfach online kaufen: www.linux-subscriptions.com

Registergericht: Amtsgericht M?nchen, Registernummer: HRB 168930, USt.-Id.:
DE209485962 | Vorstand: Thomas Merz (Vors.), Marc Grimme, Mark Hlawatschek, Jan R. Bergrath |
Vorsitzender des Aufsichtsrats: Dr. Martin Buss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: follow-service.sh.diff
Type: text/x-patch
Size: 956 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20120228/3505876f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: follow-service.sl
Type: text/x-matlab
Size: 6094 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20120228/3505876f/attachment-0001.bin>

[Cluster-devel] Small Bug in follow-service.sl

[Lon Hohberger]

On 02/28/2012 05:05 AM, Marc Grimme wrote:
> Hello,
> a few weeks ago I stumbled over an issue in the follow-service functionality in rgmanager event scripting with rind.
>
> When I wrote it I didn't think about people not having a specifically configured failover domain.
>
> But I had to setup the follow-service with a default failover domain (no failover domain configured defaults to all hosts being in the failover domain). In this case the follow-service would not work an did not start the service when a node down event was triggered.
>
> Attached you'll find the follow-service script that has this issue fixed and a patch against the latest stable RHEL6 GIT of cluster3.
>
> Regards
> Marc.
>

Merged in to STABLE32

http://git.fedorahosted.org/git?p=cluster.git;a=commit;h=c7d3938a3856f9cb295dc6aed8b7f86762cbed7c

-- Lon