Sparse ID attributes in /etc/cluster.xml cause clumanager to stop short when starting/stopping a resource. e.g. <device id="0"> <...> </device> <device id="3"> <...> </device> Version-Release number of selected component (if applicable): 1.2.3-1 - 1.2.16-1 How reproducible: 100% Steps to Reproduce: 1. Create a service with an NFS export with 3 clients. 2. Save changes. 2. Remove the middle client. 3. Save changes. Actual results: Export will not occur to 3rd-defined client. Expected results: Export occurs to 3rd-defined client. Additional info: General problem with the way the old clumanager scripts worked.
Created attachment 104070 [details] Patch fixing problem Tested. This implements sparse ID handling for all parts of a service as well as fixes a few misc. and removes some unused code.
Created attachment 104071 [details] Test case cluster.xml
Found a few minor bugs during more rigorous testing.
Bugs squashed. Waiting for errata.
Created attachment 106338 [details] My test config.
Verified with the config from #9 against version: clumanager-1.2.22-2 Ready for RHEL3-U4.
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 the 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-2004-491.html