Description of problem: No cluster configuration ever works. Has ANYBODY successfully created a working cluster? Please show a real working cluster config. Version-Release number of selected component (if applicable): F1 How reproducible: Everytime. No cluster config works Steps to Reproduce: 1. define a cluster (system-config-cluster) 2. service start cman 3. fail everytime Actual results: Expected results: Additional info:
system-config-cluster has been deprecated and cannot generate valid config files for cluster as shipped in F10/F11 or newer. This config works just fine for me. It's a bit more than what you need to start a simple cluster. <?xml version="1.0"?> <cluster name="fabbione" config_version="1" alias="fabbione"> <logging debug="off"/> <clusternodes> <clusternode name="fedora11-node1" votes="1" nodeid="1"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node1"/> </method> </fence> </clusternode> <clusternode name="fedora11-node2" votes="1" nodeid="2"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node2"/> </method> </fence> </clusternode> <clusternode name="fedora11-node3" votes="1" nodeid="3"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node3"/> </method> </fence> </clusternode> <clusternode name="fedora11-node4" votes="1" nodeid="4"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node4"/> </method> </fence> </clusternode> <clusternode name="fedora11-node5" votes="1" nodeid="5"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node5"/> </method> </fence> </clusternode> <clusternode name="fedora11-node6" votes="1" nodeid="6"> <fence> <method name="single"> <device name="virsh_fence" port="fedora11-node6"/> </method> </fence> </clusternode> </clusternodes> <fencedevices> <fencedevice name="virsh_fence" agent="fence_virsh" ipaddr="daikengo.int.fabbione.net" login="root" secure="1" identity_file="/root/.ssh/id_rsa"/> </fencedevices> <quorumd interval="1" tko="10" votes="1" label="qdisk"> <heuristic program="ping gordian.int.fabbione.net -c1 -t1" score="1" interval="2" tko="3"/> <heuristic program="ping golion.int.fabbione.net -c1 -t1" score="1" interval="2" tko="3"/> <heuristic program="ping cerberus.int.fabbione.net -c1 -t1" score="1" interval="2" tko="3"/> <heuristic program="ping vultus5.int.fabbione.net -c1 -t1" score="1" interval="2" tko="3"/> </quorumd> <rm central_processing="1"> <failoverdomains> <failoverdomain name="failover_domain1" ordered="0" restricted="0"> <failoverdomainnode name="fedora11-node1" priority="1"/> <failoverdomainnode name="fedora11-node2" priority="1"/> <failoverdomainnode name="fedora11-node3" priority="1"/> <failoverdomainnode name="fedora11-node4" priority="1"/> <failoverdomainnode name="fedora11-node5" priority="1"/> <failoverdomainnode name="fedora11-node6" priority="1"/> </failoverdomain> </failoverdomains> <resources> <ip address="192.168.0.128" monitor_link="1"/> </resources> <service autostart="1" name="vip1" domain="failover_domain1"> <ip ref="192.168.0.128"/> </service> </rm> </cluster>
Is this a dup of #473131 modulo the differing distros I wonder? I never use the config tool as I always hand edit my cluster.conf files.
If its known to be broken, why not remove it then?
Reopening as there is no point keeping known broken packages which we are not intendeding to fix. We should remove the package if that is the case.
Reassigning to myself until I can find someone better :-)