Tested on pacemaker 1.1.14-2ubuntu1.5 from xenial-proposed. Tried reproducing according to test case from description, and confirmed that pacemaker is fixed:
# apt list pacemaker
pacemaker/xenial-proposed,now 1.1.14-2ubuntu1.5 amd64 [installed]
# ls -l /tmp/pacemaker.log
-rw-rw---- 1 hacluster haclient 13695 Mar 18 14:45 /tmp/pacemaker.log
# head /tmp/pacemaker.log
Set r/w permissions for uid=112, gid=116 on /tmp/pacemaker.log
Mar 18 14:45:22 [7342] pacemaker pacemakerd: info: crm_log_init: Changed active directory to /var/lib/pacemaker/cores/root
Mar 18 14:45:22 [7342] pacemaker pacemakerd: info: get_cluster_type: Detected an active 'corosync' cluster
[...]
Tested on pacemaker 1.1.14-2ubuntu1.5 from xenial-proposed. Tried reproducing according to test case from description, and confirmed that pacemaker is fixed:
# apt list pacemaker xenial- proposed, now 1.1.14-2ubuntu1.5 amd64 [installed]
pacemaker/
# echo "PCMK_logfile= /tmp/pacemaker. log" >> /etc/default/ pacemaker
# systemctl restart pacemaker.service
# ls -l /tmp/pacemaker.log
-rw-rw---- 1 hacluster haclient 13695 Mar 18 14:45 /tmp/pacemaker.log
# head /tmp/pacemaker.log pacemaker/ cores/root
Set r/w permissions for uid=112, gid=116 on /tmp/pacemaker.log
Mar 18 14:45:22 [7342] pacemaker pacemakerd: info: crm_log_init: Changed active directory to /var/lib/
Mar 18 14:45:22 [7342] pacemaker pacemakerd: info: get_cluster_type: Detected an active 'corosync' cluster
[...]