Publishing details

Changelog

pacemaker (1.1.18-2ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
    - d/control: Demote fence-agents to Suggests, avoiding main
      inclusion.
    - 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.
  * Drop changes:
    - Drop upstreamed patches (dropped in Debian now instead).
    - Refresh d/p/portability-define-EKEYREJECTED-if-necessary.patch: no longer
      needed; dropped in Debian.
    - d/pacemaker.{pre,post}inst flag for corosync: upgrade path no longer
      needed post-Bionic.

pacemaker (1.1.18-2) unstable; urgency=medium

  * [812cda7] Fixup symbols files.
    The Hurd architecture looks strangely irregular.
  * [38d49fe] Simplify autopkgtest script
  * [87f237c] Remove trailing empty line from debian/changelog

pacemaker (1.1.18-1) unstable; urgency=medium

  * [da58a7f] Some overlooked libqb vs new binutils symbol flux
  * [c6b8c8a] New upstream release (1.1.18)
  * [871dcfa] Delete upstreamed patches, refresh the rest
  * [7c9e795] Add post-1.1.18 regression fixes
    https://lists.clusterlabs.org/pipermail/users/2017-December/014227.html
    * 1.1.18 improved scalability by eliminating redundant node attribute
    write-outs. This proved to be too aggressive in one case: when a
    cluster is configured with only IP addresses (no node names) in
    corosync.conf, attribute write-outs can be incorrectly delayed; in the
    worst case, this prevents a node from shutting down due to the shutdown
    attribute not being written.
    * 1.1.18 overhauled unfencing in order to support it on remote nodes.
    (Unfencing is for devices such as fence_scsi that require a fenced node
    to be explicitly re-admitted to the cluster.) This made the faulty
    assumption that the fence devices themselves could operate before
    unfencing happened. As a result, a cluster with unfencing could see
    unnecessary fence device monitoring failures (these do not harm the
    cluster's ability to fence or unfence).
    * 1.1.18 implemented ordering constraints for the new bundle resource
    type. This had a corner case that could lead to an invalid transition.
    As part of the fix for this, we have included a fix for an issue
    discussed in an earlier thread on this list ("pcmk_remote evaluation"),
    so the cluster will always prefer the newest Pacemaker Remote
    connection to a remote node, even if an older (dead) connection has not
    yet timed out.
  * [4d9e29c] Update Standards-Version to 4.1.4 (no changes required)
  * [c77cdf4] Migrate to salsa.debian.org/ha-team
  * [269dcb6] Switch to HTTPS in the Homepage and Source URLs
  * [371288b] Switch to Debhelper compat level 11
  * [c58d652] Replace hand-made control substitution with stock dpkg method.
    Remove the superfluous check_header_deps call as well.
  * [eb76cbd] Update symbols files

 -- Robie Basak <email address hidden>  Tue, 24 Jul 2018 14:12:03 +0100

Available diffs

Builds

Built packages

Package files