Fix XML issue in fence_watchdog meta-data
Resolves: rhbz1443666

Fix minor issue with crm_resource error message change
Resolves: rhbz1447918

Fix watchdog agent version information
Ensure transient attributes are cleared when multiple nodes are lost
Resolves: rhbz1443666
Resolves: rhbz1986998

Allow configuring specific nodes to use watchdog-only sbd for fencing
Resolves: rhbz1443666

Show better error messages in crm_resource with invalid resource types
Avoid selecting wrong device when dynamic-list fencing is used with host map
Do not schedule probes of unmanaged resources on pending nodes
Fix regressions in crm_attribute and crm_master argument handling
Resolves: rhbz1447918
Resolves: rhbz1978010
Resolves: rhbz1982453
Resolves: rhbz1984120

crm_resource now supports XML output from resource agent actions
Correct output for crm_simulate --show-failcounts
Avoid remote node unfencing loop
Resolves: rhbz1644628
Resolves: rhbz1686426
Resolves: rhbz1961857

Rebase on upstream 2.1.0 final release
Correct schema for crm_resource XML output
Resolves: rhbz1935464
Resolves: rhbz1967087

Add crm_simulate --show-attrs and --show-failcounts options
Retry getting fence agent meta-data after initial failure
Add debug option for more verbose ocf:pacemaker:ping logs
Rebase on upstream 2.1.0-rc2 release
Support OCF Resource Agent API 1.1 standard
Fix crm_mon regression that could cause certain agents to fail at shutdown
Allow setting OCF check level for crm_resource --validate and --force-check
Resolves: rhbz1686426
Resolves: rhbz1797579
Resolves: rhbz1843177
Resolves: rhbz1935464
Resolves: rhbz1936696
Resolves: rhbz1948620
Resolves: rhbz1955792

Route cancellations through correct node when remote connection is moving
Resolves: rhbz1928762

Do not introduce regression in crm_resource --locate
Resolves: rhbz1925681

crm_mon --daemonize should reconnect if cluster restarts
crm_mon should show more informative messages when cluster is starting
crm_mon should show rest of status if fencing history is unavailable
cibsecret now works on remote nodes (as long as name can be reached via ssh)
Stop remote nodes correctly when connection history is later than node history
Resolves: rhbz1466875
Resolves: rhbz1872490
Resolves: rhbz1880426
Resolves: rhbz1881537
Resolves: rhbz1898457

Allow non-critical resources that stop rather than make another resource move
Support crm_resource --digests option for showing operation digests
Clean-up of all resources should work from remote nodes
Resolves: rhbz1371576
Resolves: rhbz1872376
Resolves: rhbz1907726

Rebase on upstream 2.0.5 release
Make waiting to be pinged by sbd via pacemakerd-api the default
Resolves: rhbz1885645
Resolves: rhbz1873138

Rebase on upstream 2.0.5-rc3 release
Resolves: rhbz1885645

Rebase on upstream 2.0.5-rc2 release
Prevent ACL bypass (CVE-2020-25654)
Resolves: rhbz1885645
Resolves: rhbz1889582

crm_mon --resource option to filter output by resource
Avoid filling /dev/shm after frequent corosync errors
Allow configurable permissions for log files
Ensure ACL write permission always supersedes read
Use fence device monitor timeout for starts and probes
Allow type="integer" in rule expressions
Avoid error messages when running crm_node inside bundles
Avoid situation where promotion is not scheduled until next transition
crm_mon should show more clearly when an entire group is disabled
Rebase on upstream 2.0.5-rc1 release
Resolves: rhbz1300597
Resolves: rhbz1614166
Resolves: rhbz1647136
Resolves: rhbz1833173
Resolves: rhbz1856015
Resolves: rhbz1866573
Resolves: rhbz1874391
Resolves: rhbz1835717
Resolves: rhbz1748139
Resolves: rhbz1885645