Failure to Start a Resource Due to Incorrect Resource Configuration

Publication Date:  2015-06-30 Views:  640 Downloads:  0
Issue Description
After being configured, the floating IP address resource Res_float_ip fails to be started on both the active and standby nodes of the HACS two-node cluster.
The following error message is displayed after the crm_mon -fr1 command is executed to check resource status:
Online: [ host1 host2 ]

Full list of resources:
     Res_NIC (ocf::users:hwNIC): Started host1
     Res_float_ip (ocf::users:hwIPaddr): Stopped 
...
Migration summary:
* Node host1: 
   Res_float_ip: migration-threshold=1 fail-count=1 last-failure='Fri Mar 29 10:06:32 2013'
...
Failed actions:
    Res_float_ip_start_0 (node=host1, call=17, rc=6, status=complete): not configured
    ...

Handling Process
1. Check the information in the configure and hacs_config.ini files. Pay attention to the following information in bold:
crm configure show
linux1:/opt/hacs # crm configure show
node linux1
node linux2
primitive Res_apache ocf:heartbeat:apache \
        params configfile="/opt/lb/conf/httpd-ssl.conf" httpd-ssl="/opt/lb/bin/httpd-ssl" envfiles="/opt/lb/bin/envvars" testregex="</ *html *>" \
        meta migration-threshold="2" failure-timeout="50" \
        op start interval="0" timeout="20s" \
        op stop interval="0" timeout="20s" \
        op monitor interval="2s" role="Started" timeout="20s"
primitive Res_floatIP ocf:users:hwIPaddr \
        params ip="10.10.10.111" nic="eth0" cidr_netmask="255.255.255.0" broadcast="10.10.10.255" \
        meta migration-threshold="2" failure-timeout="50" \
        op start interval="0" timeout="20s" \
        op stop interval="0" timeout="20s" \
        op monitor interval="2s" role="Started" timeout="20s"
primitive Res_nic ocf:users:hwNIC \
        params device="eth0" \
        meta migration-threshold="2" failure-timeout="50" \
        op start interval="0" timeout="20s" \
        op stop interval="0" timeout="20s" \
        op monitor interval="2s" role="Started" timeout="20s"
group group_apache Res_nic Res_floatIP Res_apache \
        meta ordered="true"
location rsc_location1_group_apache group_apache \
        rule $id="group_apache_rule_linux1" 2720: #uname eq linux1 \
        rule $id="group_apache_rule_linux2" 2710: #uname eq linux2
property $id="cib-bootstrap-options" \
        cluster-infrastructure="openais" \
        no-quorum-policy="ignore" \
        expected-quorum-votes="2" \
        stonith-enabled="false" \
        symmetric-cluster="true" \
        default-resource-stickiness="3000" \
        cluster-delay="60s" \
        start-failure-is-fatal="false" \
        cluster-recheck-interval="1min" \
        pe-error-series-max="100" \
        pe-warn-series-max="100" \
        pe-input-series-max="100" \
        dc-version="1.0.12-f372204" \
        maintenance-mode="false"

2. Verify that information in the configure file is the same as that in the hacs_config.ini file.
crm configure edit
3. Restart the HACS core resource file.
service corosync stop
service corosync start
Root Cause
Information in the configuration file configure is different from that in the hacs_config.ini file.

END