PPA successfully built pacemaker fixes: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
and the merge request has been +1. ** Description changed: - This bug backport/cherrypick fixes released after 2.0.3 release. - The correct patches are going to be defined within this bug comments. + [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. -- 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: In Progress 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 : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
