Rebuild Corosync 2 DEB package with --enable-dbus flag

[Bogdan Dobrelya]

Please rebuild Corosync 2 package shipped with Ubuntu trusty in MOS with --enable-dbus flag.
Note, this package is required for RabbitMQ fencing improvement https://review.openstack.org/#/c/108792/ and should be kept in the testing repo

[Aleksander Mogylchenko (amogylchenko)]

Corosync 2.3.3-1, which comes with Ubuntu Trusty, has dbus support enabled.

[Bogdan Dobrelya (bogdando)]

@Aleksandr, I checked the corosync in Ubuntu and I cannot find any node left/join events from corosync in dbus-monitor.
So, it looks like it has no dbus support out of box

[Bogdan Dobrelya (bogdando)]

Here is an example message:
signal sender=:1.2 -> dest=(null destination) serial=452 path=/org/corosync; interface=org.corosync; member=NodeStateChange
   string "node-2.test.domain.local"
   uint32 2
   string "192.168.0.5"
   string "left"

and I can see them in Centos 6.5, but not in Ubuntu 14.04

[Aleksander Mogylchenko (amogylchenko)]

Have you started corosync-notifyd:
http://manpages.ubuntu.com/manpages/precise/man8/corosync-notifyd.8.html

I can see all events just fine after starting this daemon, as man page suggested:
ignal sender=:1.10 -> dest=(null destination) serial=2 path=/org/corosync; interface=org.corosync; member=QuorumStateChange
   string "vagrant-ubuntu-trusty-64"
   uint32 2130706433
   string "quorate"
signal sender=:1.10 -> dest=(null destination) serial=3 path=/org/corosync; interface=org.corosync; member=ConnectionStateChange
   string "vagrant-ubuntu-trusty-64"
   uint32 2130706433
   string "corosync-notify:9548:0x7f3c7dff9a10"
   string "connected"

[Bogdan Dobrelya (bogdando)]

Yes, I forgot to use -d option for notifyd process. With this option enabled, the events are being reported OK