~x-stride/ubuntu/+source/pacemaker:lp1864116-focal

Last commit made on 2020-02-21
Get this branch:
git clone -b lp1864116-focal https://git.launchpad.net/~x-stride/ubuntu/+source/pacemaker
Only Morten Borre can upload to this branch. If you are Morten Borre please log in for upload directions.

Branch merges

Branch information

Name:
lp1864116-focal
Repository:
lp:~x-stride/ubuntu/+source/pacemaker

Recent commits

c4fda38... by Rafael David Tinoco

update-maintainer

94dfa48... by Rafael David Tinoco

reconstruct-changelog

9eb94df... by Rafael David Tinoco

merge-changelogs

aff295b... by Rafael David Tinoco

* Fix: Last attempt i386 binary packages removal was wrong (-Nlibkate)
* Ubuntu i386 binary compatibility only effort: (LP: #1863437)
  - i386 binary package removal:
    - pacemaker
    - pacemaker-cli-utils
    - pacemaker-remote
    - pacemaker-resource-agents
  [https://salsa.debian.org/ha-team/pacemaker/merge_requests/1]

011466e... by Rafael David Tinoco

* Make crmsh the default management tool for now (LP: #1862947)

2c06e43... by Rafael David Tinoco

* Dropped: Omit pacemaker, pacemaker-cli-utils, pacemaker-remote binary
  packages on i386.
  [merged in debian/2.0.3-3]

da3391d... by Rafael David Tinoco

* Skip autopkgtest for unprivileged containers: (LP: #1828228)
  + d/t/control: mark pacemaker test as skippable
  + d/t/pacemaker: skip if memlock can't be set to unlimited by root

0652a37... by Rafael David Tinoco

* d/control: Demote fence-agents to Suggests, avoiding main inclusion.

d787f4f... by Rafael David Tinoco

* Dropped: debian/patches/pacemaker_is_partof_corosync.patch:

  Default systemd unit hard-requires corosync:
  Debian disagrees in Debian bug 887563 message 36. We could revert
  back to Debian's behaviour, but keeping the patch in this merge
  maintains existing behaviour for Ubuntu users pending any separate
  future decision.

  [Update - Rafael David Tinoco]

  - The patch still had a message saying it would be "forwaded in the
    future", but there was still an on-going discussion with HA
    maintainers.
  - I do agree with Debian HA maintainer, that pacemaker service should
    not, ever, try to continue operating if the message layer is gone.
  - The excuse that, in an upgrade event, the resource would not migrate
    and/or the node would not be fenced because pacemaker would be
    restarted by postrm/postinst right after the upgrade is weak,
    because the totem protocol is not designed to handle all ring
    networks being lost, which will happen when corosync is stopped (it
    does not matter if for a short period of time).
  - PLUS, a HA cluster node should *NOT* ever be upgraded with active
    resources on it: one can put the cluster into "Standby Mode" and
    force the migration of all services to other nodes, or put the
    entire cluster in "Maintenance Mode" and make resource agents not
    to try to manage the services anymore (so you can keep them active
    in one node, for example).
  - Message #41 in Debian Bug explicitly explains what was the real
    problem:
    """
    I have to make a correction here. The problem is not that Pacemaker
    is stopped when Corosync is upgraded, but that Pacemaker is not
    started after the Corosync upgrade is complete. So the old prerm
    stopping Corosync is not a problem: the new postinst will *restart*
    Corosync (even though it's stopped already), and the restart
    operation does start Pacemaker again. A simple start operation does
    not, but a restart does. I haven't decided yet whether this is a
    systemd bug, a quirk or a feature.
    """
  - And it was fixed in commit bellow, closing #887563:
    """
    commit e44e00f7
    Author: Ferenc Wágner <email address hidden>
    Date: Tue Apr 24 09:31:32 2018

        --restart-after-upgrade instead of stop in prerm and start in
          postinst
    """

a318e62... by =?utf-8?q?Ferenc_W=C3=A1gner?= <email address hidden>

Import patches-unapplied version 2.0.3-3 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 1a9333c2293e2fd24a827eb9747cf790c3147c0f

New changelog entries:
  * [543574f] Omit pacemaker{, -cli-utils, -remote} on Ubuntu/i386
    (Closes: #948379)
  * [327889e] Reenable dwz, it already works with the magic sections from libqb