Bug #1896223 “no-quorum-policy=demote and on-fail=demote feature...” : Bugs : pacemaker package : Ubuntu

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-22:

#1

This is the same as:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1890185

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-22:

#2

* Post 2.0.4 feature backport: on-fail="demote" recovery policy (LP: #1896223)
  debian/patches/ubuntu/lp1896223-*:
  - [c4429d86e] Log: scheduler: downgrade "active on" messages to trace
  - [01c5ec67e] Low: scheduler: match initial no-quorum-policy struct value to
  - [015b5c012] Doc: Pacemaker Explained: document no-quorum-policy=demote
  - [5d809e136] Test: scheduler: add regression test
  - [b1ae35938] Feature: scheduler: support "demote" choice
  - [0b6834453] Refactor: scheduler: functionize checking quorum policy
  - [d4b9117e7] Doc: Pacemaker Explained: correct on-fail default
  - [204961e95] Doc: Pacemaker Explained: document new on-fail="demote" option
  - [d29433ea5] Test: scheduler: add regression tests for on-fail="demote"
  - [874f75e0f] Feature: scheduler: new on-fail="demote" recovery policy
  - [2f1e2df1f] Feature: xml: add on-fail="demote" option to resources schema
  - [fd55a6660] Doc: libpacemaker: improve comments for resource state
  - [98c3b649f] Log: libpacemaker: check for re-promotes specifically
  - [ff6aebecf] Doc: libpacemaker: improve comments when logging actions
  - [f2d244bc4] Test: scheduler: test forcing a restart instead of reload
  - [a4d6a20a9] Low: libpacemaker: don't force stop when skipping reload
  - [8dceba792] Refactor: scheduler: use more appropriate types in a couple
  - [ef246ff05] Fix: scheduler: disallow on-fail=stop for stop operations
  - [f1f71b3f3] Refactor: scheduler: functionize comparing on-fail values

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-22:

#3

Release team, I would like this to be an exception so I can add a new feature to pacemaker: the on-fail="demote" recovery policy for the pacemaker policy engine.

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-22:

#4

The feature was announced by the following e-mail:

-------- Forwarded Message --------
Subject: [ClusterLabs] Coming in Pacemaker 2.0.5: on-fail=demote / no-quorum-policy=demote
Date: Mon, 10 Aug 2020 11:47:24 -0500
From: Ken Gaillot <email address hidden>
Reply-To: Cluster Labs - All topics related to open-source clustering welcomed <email address hidden>
Organization: Red Hat
To: Cluster Labs - All topics related to open-source clustering welcomed <email address hidden>

Hi all,

Looking ahead to the Pacemaker 2.0.5 release expected at the end of
this year, here is a new feature already in the master branch.

When configuring resource operations, Pacemaker lets you set an "on-
fail" policy to specify whether to restart the resource, fence the
node, etc., if the operation fails. With 2.0.5, a new possible value
will be "demote", which will mean "demote this resource but do not
fully restart it".

"Demote" will be a valid value only for promote actions, and for
recurring monitors with "role" set to "Master".

Once the resource is demoted, it will be eligible for promotion again,
so if the promotion scores have not changed, a promote on the same node
may be attempted. If this is not desired, the agent can change the
promotion scores either in the failed monitor or the demote.

The intended use case is an application where a successful demote assures a well-functioning service, and a full restart would be
unnecessarily heavyweight. A large database might be an example.

Similarly, Pacemaker offers the cluster-wide "no-quorum-policy" option
to specify what happens to resources when quorum is lost (the default
being to stop them). With 2.0.5, "demote" will be a possible value here
as well, and will mean "demote all promotable resources and stop all
other resources".

The intended use case is an application that cannot cause any harm
after being demoted, and may be useful in a demoted role even if there
is no quorum. A database that operates read-only when demoted and
doesn't depend on any non-promotable resources might be an example.

Happy clustering :)
--
Ken Gaillot <email address hidden>

The feature was announced by the following e-mail:

-------- Forwarded Message --------
Subject: [ClusterLabs] Coming in Pacemaker 2.0.5: on-fail=demote / no-quorum-policy=demote
Date: Mon, 10 Aug 2020 11:47:24 -0500
From: Ken Gaillot <kgaillot@redhat.com>
Reply-To: Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org>
Organization: Red Hat
To: Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org>

Hi all,

Looking ahead to the Pacemaker 2.0.5 release expected at the end of
this year, here is a new feature already in the master branch.

When configuring resource operations, Pacemaker lets you set an "on-
fail" policy to specify whether to restart the resource, fence the
node, etc., if the operation fails. With 2.0.5, a new possible value
will be "demote", which will mean "demote this resource but do not
fully restart it".

"Demote" will be a valid value only for promote actions, and for
recurring monitors with "role" set to "Master".

Once the resource is demoted, it will be eligible for promotion again,
so if the promotion scores have not changed, a promote on the same node
may be attempted. If this is not desired, the agent can change the
promotion scores either in the failed monitor or the demote.

The intended use case is an application where a successful demote assures a well-functioning service, and a full restart would be
unnecessarily heavyweight. A large database might be an example.

Similarly, Pacemaker offers the cluster-wide "no-quorum-policy" option
to specify what happens to resources when quorum is lost (the default
being to stop them). With 2.0.5, "demote" will be a possible value here
as well, and will mean "demote all promotable resources and stop all
other resources".

The intended use case is an application that cannot cause any harm
after being demoted, and may be useful in a demoted role even if there
is no quorum. A database that operates read-only when demoted and
doesn't depend on any non-promotable resources might be an example.

Happy clustering :)
--
Ken Gaillot <kgaillot@redhat.com>

description:	updated
Changed in pacemaker (Ubuntu Focal):
importance:	Undecided → Wishlist
Changed in pacemaker (Ubuntu):
importance:	Undecided → High

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-22:

#5

I'm now running all pacemaker cluster test suite on this pacemaker (together with latest changes in all HA stack for Groovy). Will make sure there are no regressions in this version AND this package will continue being maintained by Ubuntu Server team.

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-24:

#6

Download full text (16.1 KiB)

Summary
* Passed: iso8601 - Invalid period - []
* Passed: iso8601 - Invalid period - [2019-01-01 00:00:00Z]
* Passed: iso8601 - Invalid period - [2019-01-01 00:00:00Z/]
* Passed: iso8601 - Invalid period - [PT2S/P1M]
* Passed: iso8601 - Invalid period - [2019-13-01 00:00:00Z/P1M]
* Passed: iso8601 - Invalid period - [20191077T15/P1M]
* Passed: iso8601 - Invalid period - [2019-10-01T25:00:00Z/P1M]
* Passed: iso8601 - Invalid period - [2019-10-01T24:00:01Z/P1M]
* Passed: iso8601 - Invalid period - [PT5H/20191001T007000Z]
* Passed: iso8601 - Invalid period - [2019-10-01 00:00:80Z/P1M]
* Passed: iso8601 - Invalid period - [2019-10-01 00:00:10 +25:00/P1M]
* Passed: iso8601 - Invalid period - [20191001T000010 -00:61/P1M]
* Passed: iso8601 - Invalid period - [P1Y/2019-02-29 00:00:00Z]
* Passed: iso8601 - Invalid period - [2019-01-01 00:00:00Z/P]
* Passed: iso8601 - Invalid period - [P1Z/2019-02-20 00:00:00Z]
* Passed: iso8601 - Invalid period - [P1YM/2019-02-20 00:00:00Z]
* Passed: iso8601 - 2014-01-01 00:30:00 - 1 Hour
* Passed: iso8601 - Valid date - Feb 29 in leap year
* Passed: iso8601 - Valid date - using 'T' and offset
* Passed: iso8601 - 24:00:00 equivalent to 00:00:00 of next day
* Passed: iso8601 - 2006-W01-7
* Passed: iso8601 - 2006-W01-7 - round-trip
* Passed: iso8601 - 2006-W01-1
* Passed: iso8601 - 2006-W01-1 - round-trip
* Passed: iso8601 - 2007-W01-7
* Passed: iso8601 - 2007-W01-7 - round-trip
* Passed: iso8601 - 2007-W01-1
* Passed: iso8601 - 2007-W01-1 - round-trip
* Passed: iso8601 - 2008-W01-7
* Passed: iso8601 - 2008-W01-7 - round-trip
* Passed: iso8601 - 2008-W01-1
* Passed: iso8601 - 2008-W01-1 - round-trip
* Passed: iso8601 - 2009-W01-7
* Passed: iso8601 - 2009-W01-7 - round-trip
* Passed: iso8601 - 2009-W01-1
* Passed: iso8601 - 2009-W01-1 - round-trip
* Passed: iso8601 - 2010-W01-7
* Passed: iso8601 - 2010-W01-7 - round-trip
* Passed: iso8601 - 2010-W01-1
* Passed: iso8601 - 2010-W01-1 - round-trip
* Passed: iso8601 - 2011-W01-7
* Passed: iso8601 - 2011-W01-7 - round-trip
* Passed: iso8601 - 2011-W01-1
* Passed: iso8601 - 2011-W01-1 - round-trip
* Passed: iso8601 - 2012-W01-7
* Passed: iso8601 - 2012-W01-7 - round-trip
* Passed: iso8601 - 2012-W01-1
* Passed: iso8601 - 2012-W01-1 - round-trip
* Passed: iso8601 - 2013-W01-7
* Passed: iso8601 - 2013-W01-7 - round-trip
* Passed: iso8601 - 2013-W01-1
* Passed: iso8601 - 2013-W01-1 - round-trip
* Passed: iso8601 - 2014-W01-7
* Passed: iso8601 - 2014-W01-7 - round-trip
* Passed: iso8601 - 2014-W01-1
* Passed: iso8601 - 2014-W01-1 - round-trip
* Passed: iso8601 - 2015-W01-7
* Passed: iso8601 - 2015-W01-7 - round-trip
* Passed: iso8601 - 2015-W01-1
* Passed: iso8601 - 2015-W01-1 - round-trip
* Passed: iso8601 - 2016-W01-7
* Passed: iso8601 - 2016-W01-7 - ro...

Summary
* Passed: iso8601        - Invalid period - []
* Passed: iso8601        - Invalid period - [2019-01-01 00:00:00Z]
* Passed: iso8601        - Invalid period - [2019-01-01 00:00:00Z/]
* Passed: iso8601        - Invalid period - [PT2S/P1M]
* Passed: iso8601        - Invalid period - [2019-13-01 00:00:00Z/P1M]
* Passed: iso8601        - Invalid period - [20191077T15/P1M]
* Passed: iso8601        - Invalid period - [2019-10-01T25:00:00Z/P1M]
* Passed: iso8601        - Invalid period - [2019-10-01T24:00:01Z/P1M]
* Passed: iso8601        - Invalid period - [PT5H/20191001T007000Z]
* Passed: iso8601        - Invalid period - [2019-10-01 00:00:80Z/P1M]
* Passed: iso8601        - Invalid period - [2019-10-01 00:00:10 +25:00/P1M]
* Passed: iso8601        - Invalid period - [20191001T000010 -00:61/P1M]
* Passed: iso8601        - Invalid period - [P1Y/2019-02-29 00:00:00Z]
* Passed: iso8601        - Invalid period - [2019-01-01 00:00:00Z/P]
* Passed: iso8601        - Invalid period - [P1Z/2019-02-20 00:00:00Z]
* Passed: iso8601        - Invalid period - [P1YM/2019-02-20 00:00:00Z]
* Passed: iso8601        - 2014-01-01 00:30:00 - 1 Hour
* Passed: iso8601        - Valid date - Feb 29 in leap year
* Passed: iso8601        - Valid date - using 'T' and offset
* Passed: iso8601        - 24:00:00 equivalent to 00:00:00 of next day
* Passed: iso8601        - 2006-W01-7
* Passed: iso8601        - 2006-W01-7 - round-trip
* Passed: iso8601        - 2006-W01-1
* Passed: iso8601        - 2006-W01-1 - round-trip
* Passed: iso8601        - 2007-W01-7
* Passed: iso8601        - 2007-W01-7 - round-trip
* Passed: iso8601        - 2007-W01-1
* Passed: iso8601        - 2007-W01-1 - round-trip
* Passed: iso8601        - 2008-W01-7
* Passed: iso8601        - 2008-W01-7 - round-trip
* Passed: iso8601        - 2008-W01-1
* Passed: iso8601        - 2008-W01-1 - round-trip
* Passed: iso8601        - 2009-W01-7
* Passed: iso8601        - 2009-W01-7 - round-trip
* Passed: iso8601        - 2009-W01-1
* Passed: iso8601        - 2009-W01-1 - round-trip
* Passed: iso8601        - 2010-W01-7
* Passed: iso8601        - 2010-W01-7 - round-trip
* Passed: iso8601        - 2010-W01-1
* Passed: iso8601        - 2010-W01-1 - round-trip
* Passed: iso8601        - 2011-W01-7
* Passed: iso8601        - 2011-W01-7 - round-trip
* Passed: iso8601        - 2011-W01-1
* Passed: iso8601        - 2011-W01-1 - round-trip
* Passed: iso8601        - 2012-W01-7
* Passed: iso8601        - 2012-W01-7 - round-trip
* Passed: iso8601        - 2012-W01-1
* Passed: iso8601        - 2012-W01-1 - round-trip
* Passed: iso8601        - 2013-W01-7
* Passed: iso8601        - 2013-W01-7 - round-trip
* Passed: iso8601        - 2013-W01-1
* Passed: iso8601        - 2013-W01-1 - round-trip
* Passed: iso8601        - 2014-W01-7
* Passed: iso8601        - 2014-W01-7 - round-trip
* Passed: iso8601        - 2014-W01-1
* Passed: iso8601        - 2014-W01-1 - round-trip
* Passed: iso8601        - 2015-W01-7
* Passed: iso8601        - 2015-W01-7 - round-trip
* Passed: iso8601        - 2015-W01-1
* Passed: iso8601        - 2015-W01-1 - round-trip
* Passed: iso8601        - 2016-W01-7
* Passed: iso8601        - 2016-W01-7 - round-trip
* Passed: iso8601        - 2016-W01-1
* Passed: iso8601        - 2016-W01-1 - round-trip
* Passed: iso8601        - 2017-W01-7
* Passed: iso8601        - 2017-W01-7 - round-trip
* Passed: iso8601        - 2017-W01-1
* Passed: iso8601        - 2017-W01-1 - round-trip
* Passed: iso8601        - 2018-W01-7
* Passed: iso8601        - 2018-W01-7 - round-trip
* Passed: iso8601        - 2018-W01-1
* Passed: iso8601        - 2018-W01-1 - round-trip
* Passed: iso8601        - 2040-W01-7
* Passed: iso8601        - 2040-W01-7 - round-trip
* Passed: iso8601        - 2040-W01-1
* Passed: iso8601        - 2040-W01-1 - round-trip
* Passed: iso8601        - 2009-W53-07
* Passed: iso8601        - epoch + 2 Years 5 Months 6 Minutes
* Passed: iso8601        - 2009-01-31 + 1 Month
* Passed: iso8601        - 2009-01-31 + 2 Months
* Passed: iso8601        - 2009-01-31 + 3 Months
* Passed: iso8601        - 2009-03-31 - 1 Month
* Passed: iso8601        - 2038-01-01 + 3 Months
* Passed: cibadmin       - Validate CIB
* Passed: crm_attribute  - Configure something before erasing
* Passed: cibadmin       - Require --force for CIB erasure
* Passed: cibadmin       - Allow CIB erasure with --force
* Passed: cibadmin       - Query CIB
* Passed: crm_attribute  - Set cluster option
* Passed: cibadmin       - Query new cluster option
* Passed: cibadmin       - Query cluster options
* Passed: crm_attribute  - Set no-quorum policy
* Passed: cibadmin       - Delete nvpair
* Passed: cibadmin       - Create operation should fail
* Passed: cibadmin       - Modify cluster options section
* Passed: cibadmin       - Query updated cluster option
* Passed: crm_attribute  - Set duplicate cluster option
* Passed: crm_attribute  - Setting multiply defined cluster option should fail
* Passed: crm_attribute  - Set cluster option with -s
* Passed: crm_attribute  - Delete cluster option with -i
* Passed: crm_simulate   - Create node1 and bring it online
* Passed: crm_attribute  - Create node attribute
* Passed: cibadmin       - Query new node attribute
* Passed: crm_attribute  - Set a transient (fail-count) node attribute
* Passed: crm_failcount  - Query a fail count
* Passed: crm_attribute  - Delete a transient (fail-count) node attribute
* Passed: cibadmin       - Digest calculation
* Passed: cibadmin       - Replace operation should fail
* Passed: crm_standby    - Default standby value
* Passed: crm_standby    - Set standby status
* Passed: crm_standby    - Query standby value
* Passed: crm_standby    - Delete standby value
* Passed: cibadmin       - Create a resource
* Passed: crm_resource   - Create a resource meta attribute
* Passed: crm_resource   - Query a resource meta attribute
* Passed: crm_resource   - Remove a resource meta attribute
* Passed: crm_resource   - Create a resource attribute
* Passed: crm_resource   - List the configured resources
* Passed: crm_resource   - Require a destination when migrating a resource that is stopped
* Passed: crm_resource   - Don't support migration to non-existent locations
* Passed: cibadmin       - Create a fencing resource
* Passed: crm_simulate   - Bring resources online
* Passed: crm_resource   - Try to move a resource to its existing location
* Passed: crm_resource   - Move a resource from its existing location
* Passed: crm_resource   - Clear out constraints generated by --move
* Passed: crm_ticket     - Default ticket granted state
* Passed: crm_ticket     - Set ticket granted state
* Passed: crm_ticket     - Query ticket granted state
* Passed: crm_ticket     - Delete ticket granted state
* Passed: crm_ticket     - Make a ticket standby
* Passed: crm_ticket     - Query ticket standby state
* Passed: crm_ticket     - Activate a ticket
* Passed: crm_ticket     - Delete ticket standby state
* Passed: crm_resource   - Ban a resource on unknown node
* Passed: crm_simulate   - Create two more nodes and bring them online
* Passed: crm_resource   - Ban dummy from node1
* Passed: crm_resource   - Ban dummy from node2
* Passed: crm_simulate   - Relocate resources due to ban
* Passed: crm_resource   - Move dummy to node1
* Passed: crm_resource   - Clear implicit constraints for dummy on node2
* Passed: cibadmin       - Drop the status section
* Passed: cibadmin       - Create a clone
* Passed: crm_resource   - Create a resource meta attribute
* Passed: crm_resource   - Create a resource meta attribute in the primitive
* Passed: crm_resource   - Update resource meta attribute with duplicates
* Passed: crm_resource   - Update resource meta attribute with duplicates (force clone)
* Passed: crm_resource   - Update child resource meta attribute with duplicates
* Passed: crm_resource   - Delete resource meta attribute with duplicates
* Passed: crm_resource   - Delete resource meta attribute in parent
* Passed: crm_resource   - Create a resource meta attribute in the primitive
* Passed: crm_resource   - Update existing resource meta attribute
* Passed: crm_resource   - Create a resource meta attribute in the parent
* Passed: cibadmin       - Copy resources
* Passed: crm_resource   - Delete resource paremt meta attribute (force)
* Passed: cibadmin       - Restore duplicates
* Passed: crm_resource   - Delete resource child meta attribute
* Passed: crm_resource   - Create a resource meta attribute in dummy1
* Passed: crm_resource   - Create a resource meta attribute in dummy-group
* Passed: crm_resource   - Specify a lifetime when moving a resource
* Passed: crm_resource   - Try to move a resource previously moved with a lifetime
* Passed: crm_resource   - Ban dummy from node1 for a short time
* Passed: crm_resource   - Remove expired constraints
* Passed: crm_diff       - Create an XML patchset
* Passed: crm_mon        - Basic text output
* Passed: crm_mon        - XML output
* Passed: crm_mon        - Basic text output without node section
* Passed: crm_mon        - XML output without the node section
* Passed: crm_mon        - Text output with only the node section
* Passed: crm_mon        - Complete text output
* Passed: crm_mon        - Complete text output filtered by node
* Passed: crm_mon        - XML output filtered by node
* Passed: crm_mon        - Complete text output filtered by tag
* Passed: crm_mon        - XML output filtered by tag
* Passed: crm_mon        - Basic text output filtered by node that doesn't exist
* Passed: crm_mon        - XML output filtered by node that doesn't exist
* Passed: crm_mon        - Detailed text output
* Passed: crm_mon        - Basic text output with inactive resources
* Passed: crm_mon        - Basic text output with inactive resources, filtered by node
* Passed: crm_mon        - Text output of partially active resources
* Passed: crm_mon        - XML output of partially active resources
* Passed: crm_mon        - Text output of partially active resources, with inactive resources
* Passed: crm_mon        - Text output of partially active resources, with inactive resources, filtered by node
* Passed: crm_mon        - Text output of partially active resources, filtered by node
* Passed: cibadmin       - Configure some ACLs
* Passed: crm_attribute  - Enable ACLs
* Passed: crm_attribute  - Set cluster option
* Passed: cibadmin       - New ACL
* Passed: cibadmin       - Another ACL
* Passed: cibadmin       - Updated ACL
* Passed: cibadmin       - unknownguy: Query configuration
* Passed: crm_attribute  - unknownguy: Set enable-acl
* Passed: crm_attribute  - unknownguy: Set stonith-enabled
* Passed: cibadmin       - unknownguy: Create a resource
* Passed: cibadmin       - l33t-haxor: Query configuration
* Passed: crm_attribute  - l33t-haxor: Set enable-acl
* Passed: crm_attribute  - l33t-haxor: Set stonith-enabled
* Passed: cibadmin       - l33t-haxor: Create a resource
* Passed: cibadmin       - niceguy: Query configuration
* Passed: crm_attribute  - niceguy: Set enable-acl
* Passed: crm_attribute  - niceguy: Set stonith-enabled
* Passed: cibadmin       - niceguy: Create a resource
* Passed: cibadmin       - root: Query configuration
* Passed: crm_attribute  - root: Set stonith-enabled
* Passed: cibadmin       - root: Create a resource
* Passed: crm_resource   - l33t-haxor: Create a resource meta attribute
* Passed: crm_resource   - l33t-haxor: Query a resource meta attribute
* Passed: crm_resource   - l33t-haxor: Remove a resource meta attribute
* Passed: crm_resource   - niceguy: Create a resource meta attribute
* Passed: crm_resource   - niceguy: Query a resource meta attribute
* Passed: crm_resource   - niceguy: Remove a resource meta attribute
* Passed: crm_resource   - niceguy: Create a resource meta attribute
* Passed: cibadmin       - badidea: Query configuration - implied deny
* Passed: cibadmin       - betteridea: Query configuration - explicit deny
* Passed: cibadmin       - niceguy: Replace - remove acls
* Passed: cibadmin       - niceguy: Replace - create resource
* Passed: cibadmin       - niceguy: Replace - modify attribute (deny)
* Passed: cibadmin       - niceguy: Replace - delete attribute (deny)
* Passed: cibadmin       - niceguy: Replace - create attribute (deny)
* Passed: cibadmin       - bob: Replace - create attribute (allow)
* Passed: cibadmin       - bob: Replace - modify attribute (allow)
* Passed: cibadmin       - bob: Replace - delete attribute (allow)
* Passed: cibadmin       - root: Upgrade to latest CIB schema
* Passed: cibadmin       - unknownguy: Query configuration
* Passed: crm_attribute  - unknownguy: Set enable-acl
* Passed: crm_attribute  - unknownguy: Set stonith-enabled
* Passed: cibadmin       - unknownguy: Create a resource
* Passed: cibadmin       - l33t-haxor: Query configuration
* Passed: crm_attribute  - l33t-haxor: Set enable-acl
* Passed: crm_attribute  - l33t-haxor: Set stonith-enabled
* Passed: cibadmin       - l33t-haxor: Create a resource
* Passed: cibadmin       - niceguy: Query configuration
* Passed: crm_attribute  - niceguy: Set enable-acl
* Passed: crm_attribute  - niceguy: Set stonith-enabled
* Passed: cibadmin       - niceguy: Create a resource
* Passed: cibadmin       - root: Query configuration
* Passed: crm_attribute  - root: Set stonith-enabled
* Passed: cibadmin       - root: Create a resource
* Passed: crm_resource   - l33t-haxor: Create a resource meta attribute
* Passed: crm_resource   - l33t-haxor: Query a resource meta attribute
* Passed: crm_resource   - l33t-haxor: Remove a resource meta attribute
* Passed: crm_resource   - niceguy: Create a resource meta attribute
* Passed: crm_resource   - niceguy: Query a resource meta attribute
* Passed: crm_resource   - niceguy: Remove a resource meta attribute
* Passed: crm_resource   - niceguy: Create a resource meta attribute
* Passed: cibadmin       - badidea: Query configuration - implied deny
* Passed: cibadmin       - betteridea: Query configuration - explicit deny
* Passed: cibadmin       - niceguy: Replace - remove acls
* Passed: cibadmin       - niceguy: Replace - create resource
* Passed: cibadmin       - niceguy: Replace - modify attribute (deny)
* Passed: cibadmin       - niceguy: Replace - delete attribute (deny)
* Passed: cibadmin       - niceguy: Replace - create attribute (deny)
* Passed: cibadmin       - bob: Replace - create attribute (allow)
* Passed: cibadmin       - bob: Replace - modify attribute (allow)
* Passed: cibadmin       - bob: Replace - delete attribute (allow)
* Passed: cibadmin       - Try to make resulting CIB invalid (enum violation)
* Passed: crm_simulate   - Run crm_simulate with invalid CIB (enum violation)
* Passed: cibadmin       - Try to make resulting CIB invalid (unrecognized validate-with)
* Passed: crm_simulate   - Run crm_simulate with invalid CIB (unrecognized validate-with)
* Passed: cibadmin       - Try to make resulting CIB invalid, but possibly recoverable (valid with X.Y+1)
* Passed: crm_simulate   - Run crm_simulate with invalid, but possibly recoverable CIB (valid with X.Y+1)
* Passed: cibadmin       - Make resulting CIB valid, although without validate-with attribute
* Passed: crm_simulate   - Run crm_simulate with valid CIB, but without validate-with attribute
* Passed: cibadmin       - Make resulting CIB invalid, and without validate-with attribute
* Passed: crm_simulate   - Run crm_simulate with invalid CIB, also without validate-with attribute
* Passed: crm_attribute  - Set stonith-enabled=false
* Passed: cibadmin       - Configure the initial resource
* Passed: cibadmin       - Upgrade to latest CIB schema (trigger 2.10.xsl + the wrapping)
* Passed: crm_resource   - Query a resource instance attribute (shall survive)
* Passed: crm_rule       - Try to check a rule that doesn't exist
* Passed: crm_rule       - Try to check a rule that has too many date_expressions
* Passed: crm_rule       - Verify basic rule is expired
* Passed: crm_rule       - Verify basic rule worked in the past
* Passed: crm_rule       - Verify basic rule is not yet in effect
* Passed: crm_rule       - Verify date_spec rule with years has expired
* Passed: crm_rule       - Verify date_spec rule with years is in effect
* Passed: crm_rule       - Try to check a rule whose date_spec does not contain years=
* Passed: crm_rule       - Try to check a rule whose date_spec contains years= and moon=
* Passed: crm_rule       - Try to check a rule with no date_expression
278 tests passed

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-24:

#7

Download full text (5.0 KiB)

$ ./CTSlab.py --nodes "groovy01 groovy02 groovy03" --once --no-loop-tests --no-unsafe-tests --outputfile ~/cts.log
Sep 24 04:40:29 >>>>>>>>>>>>>>>> BEGINNING 15 TESTS
Sep 24 04:40:29 Stack: corosync 2+ (crm-corosync)
Sep 24 04:40:29 Schema: pacemaker-3.0
Sep 24 04:40:29 Scenario: Every Test Once
Sep 24 04:40:29 CTS Master: 10.250.97.104
Sep 24 04:40:29 CTS Logfile: /home/rafaeldtinoco/cts.log
Sep 24 04:40:29 Random Seed: 1600922428
Sep 24 04:40:29 Syslog variant: rsyslog
Sep 24 04:40:29 System log files: /var/log/messages
Sep 24 04:40:29 Cluster starts at boot: 1
Sep 24 04:40:29 Cluster nodes:
Sep 24 04:40:29 * groovy01
Sep 24 04:40:29 * groovy02
Sep 24 04:40:29 * groovy03
Sep 24 04:40:32 Writing log with key: 02c86ca5-acb3-4498-bfa6-726a53b23da6
Sep 24 04:40:32 Testing for combined syslog logs
Sep 24 04:40:38 Testing for journal logs
Sep 24 04:40:39 Continuing with journal-based log reader
Sep 24 04:40:45 Stopping crm-corosync on node groovy01
Sep 24 04:40:50 Stopping crm-corosync on node groovy02
Sep 24 04:40:55 Stopping crm-corosync on node groovy03
Sep 24 04:40:57 Starting Cluster Manager on all nodes.
Sep 24 04:40:59 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy01
Sep 24 04:41:28 Starting crm-corosync on node groovy02
Sep 24 04:41:29 Starting crm-corosync on node groovy03
Sep 24 04:41:50 Running test Flip (groovy03) [ 1]
Sep 24 04:42:34 Running test Restart (groovy01) [ 2]
Sep 24 04:43:00 Running test Stonithd (groovy03) [ 3]
Sep 24 04:44:07 Running test StartOnebyOne (groovy03) [ 4]
Sep 24 04:46:29 Running test SimulStart (groovy02) [ 5]
Sep 24 04:47:23 Running test SimulStop (groovy03) [ 6]
Sep 24 04:47:39 Running test StopOnebyOne (groovy03) [ 7]
Sep 24 04:48:44 Running test RestartOnebyOne (groovy02) [ 8]
Sep 24 04:50:23 Running test PartialStart (groovy03) [ 9]
Sep 24 04:51:08 Running test Standby (groovy02) [ 10]
Sep 24 04:52:03 Running test MaintenanceMode (groovy01) [ 11]
Sep 24 04:52:26 Running test ResourceRecover (groovy03) [ 12]
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33 Test ResourceRecover FAILED: fence-groovy01 was not recovered and is inactive
Sep 24 04:52:41 Running test Reattach (groovy03) [ 13]
Sep 24 04:54:03 Running test SpecialTest1 (groovy02) [ 14]
Sep 24 04:55:05 Running test NearQuorumPoint (groovy02) [ 15]
Sep 24 04:55:20 Stopping Cluster Manager on all nodes
Sep 24 04:55:20 Stopping crm-corosync on node groovy03
Sep 24 04:55:28 ****************
Sep 24 04:55:28 Ove...

$ ./CTSlab.py --nodes "groovy01 groovy02 groovy03" --once --no-loop-tests --no-unsafe-tests --outputfile ~/cts.log
Sep 24 04:40:29	>>>>>>>>>>>>>>>> BEGINNING 15 TESTS
Sep 24 04:40:29	Stack:                  corosync 2+ (crm-corosync)
Sep 24 04:40:29	Schema:                 pacemaker-3.0
Sep 24 04:40:29	Scenario:               Every Test Once
Sep 24 04:40:29	CTS Master:             10.250.97.104
Sep 24 04:40:29	CTS Logfile:            /home/rafaeldtinoco/cts.log
Sep 24 04:40:29	Random Seed:            1600922428
Sep 24 04:40:29	Syslog variant:         rsyslog
Sep 24 04:40:29	System log files:       /var/log/messages
Sep 24 04:40:29	Cluster starts at boot: 1
Sep 24 04:40:29	Cluster nodes:
Sep 24 04:40:29	* groovy01
Sep 24 04:40:29	* groovy02
Sep 24 04:40:29	* groovy03
Sep 24 04:40:32	Writing log with key: 02c86ca5-acb3-4498-bfa6-726a53b23da6
Sep 24 04:40:32	Testing for combined syslog logs
Sep 24 04:40:38	Testing for journal logs
Sep 24 04:40:39	Continuing with journal-based log reader
Sep 24 04:40:45	Stopping crm-corosync on node groovy01
Sep 24 04:40:50	Stopping crm-corosync on node groovy02
Sep 24 04:40:55	Stopping crm-corosync on node groovy03
Sep 24 04:40:57	Starting Cluster Manager on all nodes.
Sep 24 04:40:59	Starting crm-corosync on node groovy01
Sep 24 04:41:28	Starting crm-corosync on node groovy01
Sep 24 04:41:28	Starting crm-corosync on node groovy02
Sep 24 04:41:29	Starting crm-corosync on node groovy03
Sep 24 04:41:50	Running test Flip                   (groovy03)    [  1]
Sep 24 04:42:34	Running test Restart                (groovy01)    [  2]
Sep 24 04:43:00	Running test Stonithd               (groovy03)    [  3]
Sep 24 04:44:07	Running test StartOnebyOne          (groovy03)    [  4]
Sep 24 04:46:29	Running test SimulStart             (groovy02)    [  5]
Sep 24 04:47:23	Running test SimulStop              (groovy03)    [  6]
Sep 24 04:47:39	Running test StopOnebyOne           (groovy03)    [  7]
Sep 24 04:48:44	Running test RestartOnebyOne        (groovy02)    [  8]
Sep 24 04:50:23	Running test PartialStart           (groovy03)    [  9]
Sep 24 04:51:08	Running test Standby                (groovy02)    [ 10]
Sep 24 04:52:03	Running test MaintenanceMode        (groovy01)    [ 11]
Sep 24 04:52:26	Running test ResourceRecover        (groovy03)    [ 12]
Sep 24 04:52:33	Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33	Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33	Command '/usr/lib/pacemaker/cts-exec-helper -R -r fence-groovy01' failed. Binary or pacemaker-cts package not installed?
Sep 24 04:52:33	Test ResourceRecover                FAILED: fence-groovy01 was not recovered and is inactive
Sep 24 04:52:41	Running test Reattach               (groovy03)    [ 13]
Sep 24 04:54:03	Running test SpecialTest1           (groovy02)    [ 14]
Sep 24 04:55:05	Running test NearQuorumPoint        (groovy02)    [ 15]
Sep 24 04:55:20	Stopping Cluster Manager on all nodes
Sep 24 04:55:20	Stopping crm-corosync on node groovy03
Sep 24 04:55:28	****************
Sep 24 04:55:28	Overall Results:{'success': 14, 'failure': 1, 'BadNews': 0, 'skipped': 0}
Sep 24 04:55:28	****************
Sep 24 04:55:28	Test Summary
Sep 24 04:55:28	Test Flip:                {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test Restart:             {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test Stonithd:            {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test StartOnebyOne:       {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test SimulStart:          {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test SimulStop:           {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test StopOnebyOne:        {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test RestartOnebyOne:     {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test PartialStart:        {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test Standby:             {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test MaintenanceMode:     {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test ResourceRecover:     {'calls': 1, 'failure': 1, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test Reattach:            {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test SpecialTest1:        {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	Test NearQuorumPoint:     {'calls': 1, 'failure': 0, 'skipped': 0, 'auditfail': 0}
Sep 24 04:55:28	<<<<<<<<<<<<<<<< TESTS COMPLETED

The test that fails does it because we have a debian patch removing
"cts-exec-helper" from the Debian package. This is part of creating the
pacemaker-cts package in order to have full regression tests before releases.

It's all good with this new merge.

description:

updated

Rafael David Tinoco (rafaeldtinoco) on 2020-09-24

summary:

- [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
+ [FFe] this is the no-quorum-policy feature (specially for mssql server)

Rafael David Tinoco (rafaeldtinoco) on 2020-09-26

summary:

- [FFe] this is the no-quorum-policy feature (specially for mssql server)
+ [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL
+ servers

Rafael David Tinoco (rafaeldtinoco) on 2020-09-28

summary:

- [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL
- servers
+ no-quorum-policy=demote and on-fail=demote features for MSSQL servers

Revision history for this message

Steve Langasek (vorlon) wrote on 2020-09-28:

#8

FFe approved.

Changed in pacemaker (Ubuntu):
status:	New → Triaged

Rafael David Tinoco (rafaeldtinoco) on 2020-09-29

Changed in pacemaker (Ubuntu):
status:	Triaged → Fix Committed
importance:	High → Undecided

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-09-29:

#9

This bug was fixed in the package pacemaker - 2.0.4-2ubuntu3

---------------
pacemaker (2.0.4-2ubuntu3) groovy; urgency=medium

  * Post 2.0.4 features: on-fail=demote & no-quorum-policy=demote
    (LP: #1896223). Added debian/patches/ubuntu/lp1896223-*:
    - [c4429d86e] Log: scheduler: downgrade "active on" messages to trace
    - [01c5ec67e] Low: scheduler: match initial no-quorum-policy struct value
    - [015b5c012] Doc: Pacemaker Explained: document no-quorum-policy=demote
    - [5d809e136] Test: scheduler: add regression test
    - [b1ae35938] Feature: scheduler: support "demote" choice
    - [0b6834453] Refactor: scheduler: functionize checking quorum policy
    - [d4b9117e7] Doc: Pacemaker Explained: correct on-fail default
    - [204961e95] Doc: Pacemaker Explained: document new on-fail="demote"
    - [d29433ea5] Test: scheduler: add regression tests for on-fail="demote"
    - [874f75e0f] Feature: scheduler: new on-fail="demote" recovery policy
    - [2f1e2df1f] Feature: xml: add on-fail="demote" option to resources
    - [fd55a6660] Doc: libpacemaker: improve comments for resource state
    - [98c3b649f] Log: libpacemaker: check for re-promotes specifically
    - [ff6aebecf] Doc: libpacemaker: improve comments when logging actions
    - [f2d244bc4] Test: scheduler: test forcing a restart instead of reload
    - [a4d6a20a9] Low: libpacemaker: don't force stop when skipping reload
    - [8dceba792] Refactor: scheduler: use more appropriate types in a couple
    - [ef246ff05] Fix: scheduler: disallow on-fail=stop for stop operations
    - [f1f71b3f3] Refactor: scheduler: functionize comparing on-fail values

-- Rafael David Tinoco <email address hidden> Tue, 22 Sep 2020 17:51:03 +0000

Changed in pacemaker (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-09-30:

#10

I have just proposed a merge at:

https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391596

but first I need the SRU on:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762

to be accepted, so I can move with this feature merge.

Will run functional/regression tests against this merge request and inform there.

Changed in pacemaker (Ubuntu Focal):
importance:	Wishlist → Undecided
status:	New → In Progress

Revision history for this message

Rafael David Tinoco (rafaeldtinoco) wrote on 2020-10-05:

#11

I had to do a new MP for LP: #1881762 (a more minimal approach) and, with that, I'll need to rebase this one (and probably re-think it based on conversations for that SRU). Doing that...

Revision history for this message

Lucas Kanashiro (lucaskanashiro) wrote on 2021-02-08:

#12

FWIW here you can find the proposed package targeting Focal for testing:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/pacemaker-sql-server

Lucas Kanashiro (lucaskanashiro) on 2021-05-17

description:

updated

Lucas Kanashiro (lucaskanashiro) on 2021-05-17

description:

updated

Revision history for this message

Robie Basak (racb) wrote on 2021-06-02:

#13

Thank you for working on this. This new pacemaker feature does sound like a worthwhile addition. However, I think there's a policy question of whether it is acceptable to add this in a stable Ubuntu release. I don't think we've done something like this before for this category of package.

I appreciate that it'd be a new opt-in feature that shouldn't change behaviour for existing users. However, there's still a regression risk and users who don't want the feature will nevertheless have no choice but to receive the update. We need to decide whether this fits user expectations about our LTS releases.

I believe this would be a policy decision that's already delegated by the technical board to the SRU team. I'll consult with other SRU team members to make this decision.

Revision history for this message

Brian Murray (brian-murray) wrote on 2021-06-08: Please test proposed package

#14

Hello Rafael, or anyone else affected,

Accepted pacemaker into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/2.0.3-3ubuntu4.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in pacemaker (Ubuntu Focal):
status:	In Progress → Fix Committed
tags:	added: verification-needed verification-needed-focal

Revision history for this message

Robie Basak (racb) wrote on 2021-07-05:

#16

trimmedpacemaker.log Edit (331.0 KiB, text/html)

Tejas successfully verified 2.0.3-3ubuntu4.3. Attached is a trimmed pacemaker log which shows SQL in action on how it uses the demote feature successfully avoiding fencing while promoting a new node.

tags:

added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal

Revision history for this message

Chris Halse Rogers (raof) wrote on 2021-07-07: Update Released

#17

The verification of the Stable Release Update for pacemaker has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2021-07-07:

#18

This bug was fixed in the package pacemaker - 2.0.3-3ubuntu4.3

---------------
pacemaker (2.0.3-3ubuntu4.3) focal; urgency=medium

  [ Rafael David Tinoco ]
  * Post 2.0.3 features: on-fail=demote & no-quorum-policy=demote
    (LP: #1896223). Added debian/patches/ubuntu-2.0.3-demote/*:
    - lp1896223-01-f1f71b3-Refactor-scheduler-functionize-comparing-on-fail.patch
    - lp1896223-02-ef246ff-Fix-scheduler-disallow-on-fail-stop-for-stop.patch
    - lp1896223-03-8dceba7-Refactor-scheduler-use-more-appropriate-types.patch
    - lp1896223-04-a4d6a20-Low-libpacemaker-don-t-force-stop-when-skipping.patch
    - lp1896223-05-98c3b64-Log-libpacemaker-check-for-re-promotes-specifically.patch
    - lp1896223-06-2f1e2df-Feature-xml-add-on-fail-demote-option-to-resources.patch
    - lp1896223-07-874f75e-Feature-scheduler-new-on-fail-demote-recovery-policy.patch
    - lp1896223-08-7eec572-Build-libcrmcommon-bump-CRM-feature-set.patch
    - lp1896223-09-204961e-Doc-Pacemaker-Explained-document-new-on-fail.patch
    - lp1896223-10-015b5c0-Doc-Pacemaker-Explained-document-no-quorum.patch
    - lp1896223-11-0b68344-Refactor-scheduler-functionize-checking-quorum.patch
    - lp1896223-12-b1ae359-Feature-scheduler-support-demote-choice-for.patch
    - lp1896223-13-d4b9117-Doc-Pacemaker-Explained-correct-on-fail-default.patch

-- Lucas Kanashiro <email address hidden> Wed, 09 Dec 2020 10:27:00 -0300

Changed in pacemaker (Ubuntu Focal):
status:	Fix Committed → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	pacemaker (Ubuntu)	Fix Released	Undecided	Unassigned
	Focal	Fix Released	Undecided	Unassigned

Ubuntu
pacemaker package

no-quorum-policy=demote and on-fail=demote features for MSSQL servers

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntupacemaker package

no-quorum-policy=demote and on-fail=demote features for MSSQL servers

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
pacemaker package