[Pacemaker] Resource only failsover in one direction

[Lucas Brown]

> Date: Tue, 22 Oct 2013 09:32:59 +0200
> From: emmanuel segura <emi2fast at gmail.com>
> To:
> 	"CAE7pJ3Av7TBgCFJya5LEAyQwEW4SFeCsrLo55WQrfjV7jOodMQ at mail.gmail.com"
> 	<CAE7pJ3Av7TBgCFJya5LEAyQwEW4SFeCsrLo55WQrfjV7jOodMQ at mail.gmail.com>,
> 	The Pacemaker cluster resource manager <pacemaker at oss.clusterlabs.org>
> Subject: Re: [Pacemaker] Resource only failsover in one direction
> Message-ID:
> 	<CAE7pJ3CM=1VbKbgBRi1CcvYy8TvuicFmg_0Lqp66N7-T2btRqQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> OCF_ROOT=/usr/lib/ocf/ OCF_RESKEY_configfile="/etc/nginx/nginx.conf"
> /usr/lib/ocf/resource.d/heartbeat/nginx start

Alright, I think we're making some progress. I did as you said and I was able to get the resource running on the second node manually.

root at lb02:~# export OCF_ROOT="/usr/lib/ocf/"
root at lb02:~# export OCF_RESKEY_configfile="/etc/nginx/nginx.conf"
root at lb02:~# /usr/lib/ocf/resource.d/heartbeat/nginx start
nginx[6360]: INFO: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful
nginx[6360]: INFO: Starting /usr/sbin/nginx - nginx version: nginx/1.1.19
nginx[6360]: INFO: /usr/sbin/nginx build configuration: configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-log-path=/var/log/nginx/access.log --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --lock-path=/var/lock/nginx.lock --pid-path=/var/run/nginx.pid --with-debug --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_realip_module --with-http_stub_status_module --with-http_ssl_module --with-http_sub_module --with-http_xslt_module --with-ipv6 --with-sha1=/usr/include/openssl --with-md5=/usr/include/openssl --with-mail --with-mail_ssl_module --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-auth-pam --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-echo --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-dav-ext-module

I did a crm resource cleanup nginx, and indeed crm showed it was running happily.

This is where it got interesting; I repaired nginx on node 1 and did a crm resource cleanup and it immediately moved it back to node 1 again, even though I have a resource stickiness of 100 in my config. Given my config seems okay, what could be causing this?

Here's my config again for reference:

node $id="724150464" lb01 \
	attributes standby="off"
node $id="740927680" lb02 \
	attributes standby="off"
primitive nginx ocf:heartbeat:nginx \
	params configfile="/etc/nginx/nginx.conf" \
	op monitor interval="10s" timeout="30s" depth="0" \
	op monitor interval="15s" timeout="30s" status10url="http://localhost/nginx_status" depth="10" \
	meta target-role="Started"
property $id="cib-bootstrap-options" \
	dc-version="1.1.10-42f2063" \
	cluster-infrastructure="corosync" \
	stonith-enabled="false" \
	no-quorum-policy="ignore" \
	start-failure-is-fatal="false" \
	last-lrm-refresh="1382570979"
rsc_defaults $id="rsc-options" \
	resource-stickiness="100"