This bug was fixed in the package pacemaker - 2.0.3-3ubuntu3

---------------
pacemaker (2.0.3-3ubuntu3) focal; urgency=medium

  * Post 2.0.3 release fixes backported to Ubuntu (LP: #1870235)
    debian/patches/ubuntu-2.0.3-fixes/:
    - lp1870235-0a8e789f9-Fix-libpengine-Options-should-be-uint.patch
    - lp1870235-186042bcb-Ref-libcrmservice-SIGCHLD-handling.patch
    - lp1870235-28bfd00e9-Low-libcrmservice-handle-child-wait-errors.patch
    - lp1870235-426f06cc0-Fix-tools-Fix-curses_indented_printf.patch
    - lp1870235-4f5207a28-Fix-tools-Correct-crm_mon-man-page.patch
    - lp1870235-5afe84e45-Fix-libstonithd-validate-arg-non-const.patch
    - lp1870235-c98987824-Fix-iso8601-Fix-crm_time_parse_offset.patch
    - lp1870235-dec326391-Log-libcrmcommon-correct-log-line-length.patch
    - lp1870235-e35908c79-Log-libcrmservice-impr-msgs-wait-child.patch
    - lp1870235-eaaa20949-Fix-libstonithd-tools-Fix-arg-stonith-event.patch
    - lp1870235-f0fe45806-Fix-scheduler-cluster-maint-mode-true.patch

 -- Rafael David Tinoco <[email protected]>  Mon, 06 Apr 2020
10:48:48 -0300

** Changed in: pacemaker (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1870235

Title:
  [focal] pacemaker v2.0.3 last upstream fixes

Status in pacemaker package in Ubuntu:
  Fix Released

Bug description:
  
  [Impact]

  * Idea here is latest release stabilization with backports of fixes
  released after the current version.

  * Since this is a LTS, it is worth applying "straightforward" fixes
  before the final release.

  [Test Case]

  * https://discourse.ubuntu.com/t/ubuntu-high-availability-corosync-
  pacemaker-shared-disk-environments/

  [Regression Potential]

  Areas of potential regression: stonith, pengine, crmservice:

  * stonith: I have regression tests and they look good.

  * pengine: could not identify bad decisions when fencing resources but
  haven't explored in detail as there are many possible combinations and
  decisions that pengine can take -> changes are very minimal here.

  * crmservice: pacemaker tests don't show regressions, resource agents
  start/stop/probe/migrate correctly afaik so the fix looks good.

  [Other Info]

  * This bug backport/cherrypick fixes released after 2.0.3 release.

  * The correct patches are going to be defined within this bug
  comments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1870235/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to