[Debian-ha-maintainers] Bug#833357: corosync: Update to 2.3.6 fails with specific configuration / upstream fixed

[Patrick Matthäi]

Package: corosync
Version: 2.3.6-2
Severity: serious
Tags: patch upstream

Hi,

updating corosync from 2.3.5 to 2.3.6 fails with some configurations (as I
already reported to the bpo list) with:
"can't autogenerate multicast address"

Upstream report and patch: https://github.com/corosync/corosync/issues/137

Please apply the patch and I would also welcome updated backports packages :)

Here is one of my /etc/corosync/corosync.conf configurations, with that it is
reproduceable:

totem {
        version: 2
        token: 3000
        token_retransmits_before_loss_const: 10
        clear_node_high_bit: yes
        crypto_cipher: none
        crypto_hash: none
        transport: udpu
        interface {
                ringnumber: 0
                bindnetaddr: 192.168.99.0
        }
}

logging {
        to_logfile: yes
        logfile: /var/log/corosync/corosync.log
        debug: off
        timestamp: on
        logger_subsys {
                subsys: QUORUM
                debug: off
        }
}

quorum {
        provider: corosync_votequorum
        two_node: 1
        wait_for_all: 1
}

nodelist {
        node {
                ring0_addr: nd1-1-cs
        }
        node {
                ring0_addr: nd1-2-cs
        }
}



-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)