Previous cluster Release Tests

Alteeve Wiki :: Previous cluster Release Tests

These are archival records of RHCS Release Manager passed results.

Testing v3.1.8

The machines being used to build the cluster need to have the following two packages installed;

yum -y install fence-agents resource-agents modcluster ricci

Now make sure that ricci is running and that selinux, iptables and ip6tables are off.

sed -e "s/SELINUX=enforcing/SELINUX=disabled/" -i /etc/selinux/config
systemctl disable ip6tables.service
systemctl disable iptables.service
systemctl enable modclusterd.service
systemctl enable ricci.service
systemctl stop ip6tables.service
systemctl stop iptables.service
systemctl start modclusterd.service
systemctl restart ricci.service

Reboot if selinux was updated.

Distro Build Tests

Distro	Arch	Date tested (YYYY-MM-DD)	Results	Notes
Fedora Rawhide	x86_64	2011-12-03	Success
Fedora Rawhide	i386	2011-12-03	Success
Fedora 16	x86_64	2011-12-03	Success
Fedora 16	i386	2011-12-03	Success
Fedora 15	x86-64	2011-12-03	Success
Fedora 15	i386	2011-12-03	Success
Ubuntu 11.10	amd64	2011-12-03	Success
Ubuntu 11.10	i386	2011-12-03	Success

Cluster Tests

Host Nodes are Fedora 16, x86_64.

Test	Result	Notes
Install via make install	Pass
Full Cluster Start	Pass
Withdraw One Node, Retain Quorum	Pass
Withdraw Second Node, Drop Quorum	Pass
Push out updated cluster.conf	Pass
Start the service via rgmanager	Pass
Manual relocate the service	Pass
Fence node/recover service	Failed	This may well be a configuration issue. fence_node test-node-3 fence test-node-3 failed Syslog; Dec 6 00:50:15 test-node-1 fence_node[3744]: fence test-node-3 failed

Cluster configuration used;

<?xml version="1.0"?>
<cluster config_version="1" name="rm-cluster">
        <totem rrp_mode="none" secauth="off" />
        <clusternodes>
                <clusternode name="test-node-1.alteeve.com" nodeid="1">
                        <fence>
                                <method name="virt">
                                        <device action="reboot" name="virt-1" port="test-node-1" />
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="test-node-2.alteeve.com" nodeid="2">
                        <fence>
                                <method name="virt">
                                        <device action="reboot" name="virt-1" port="test-node-2" />
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="test-node-3.alteeve.com" nodeid="3">
                        <fence>
                                <method name="virt">
                                        <device action="reboot" name="virt-1" port="test-node-3" />
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <fencedevices>
                <fencedevice name="virt-1" agent="fence_virsh" ipaddr="192.168.1.102" login="root" passwd="secret" />
        </fencedevices>
        <rm log_level="5">
                <resources>
                        <ip address="192.168.1.30" />
                </resources>
                <failoverdomains>
                        <failoverdomain name="virt-ip" nofailback="0" ordered="1" restricted="0">
                                <failoverdomainnode name="test-node-1.alteeve.com" priority="1" />
                                <failoverdomainnode name="test-node-2.alteeve.com" priority="2" />
                                <failoverdomainnode name="test-node-3.alteeve.com" priority="3" />
                        </failoverdomain>
                </failoverdomains>
                <service autostart="1" domain="virt-ip" name="float_ip" recovery="relocate">
                        <ip ref="192.168.1.30" />
                </service>
        </rm>
</cluster>

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche!	Alteeve Enterprise Support	Community Support
© 2025 Alteeve. Intelligent Availability® is a registered trademark of Alteeve's Niche! Inc. 1997-2025
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.