Root case of the issue is next. After adding upstart job for corosync-notifyd (Change-Id: I6b3abb5a65a0a73db1642800dfa01b1a46192197), /usr/sbin/corosync-notifyd had been launching without '-b' option. This option is needed in order to run corosync-notifyd as a daemon. So in fact corosync-notifyd wasn't running on corosync nodes, that's why no signals have been sent to dbus and rabbit-fence.py script wasn't able to react on such situations.
Introduced patch adds '-d' option in OPTIONS environment variable to /etc/default/corosync-notifyd
Root case of the issue is next. After adding upstart job for corosync-notifyd (Change-Id: I6b3abb5a65a0a7 3db1642800dfa01 b1a46192197) , /usr/sbin/ corosync- notifyd had been launching without '-b' option. This option is needed in order to run corosync-notifyd as a daemon. So in fact corosync-notifyd wasn't running on corosync nodes, that's why no signals have been sent to dbus and rabbit-fence.py script wasn't able to react on such situations. corosync- notifyd
Introduced patch adds '-d' option in OPTIONS environment variable to /etc/default/