Reid Wahl

`crm configure` requires both `deprecated` and `obsoletes` params

4

If a resource's metadata contains a deprecated param (`deprecated="1"`) and a new one that obsoletes it, and both params have `required="1"`, then `crm configure` requires both parameters. This is unexpected...

Unit tests for some env option functions

3

Closes [T493](lib/common/tests/options/Makefile.am).

Test: cts: Reimplement cts-regression in Python

4

Closes T498

Fix: libpacemaker: Don't shuffle anonymous clone instances unnecessarily

22

Fix: libpacemaker: Don't shuffle anonymous clone instances Currently, anonymous clone instances may be shuffled under certain conditions, causing an unnecessary resource downtime when an instance is moved away from its...

WIP: Refactor: libcrmcommon: Introduce GString for XML

1

**WIP** Update `xml.c` and `acl.c` to use `GString` in a couple of places for dynamic allocation. Eliminates risk of overflowing `char` array. Resolves: RHBZ#1822125 --- I'd like to get maintainers'...

Doc: pcmk_action_timeout update

6

The default `pcmk__timeout` values listed in the doc are incorrect in my experience. The monitor timeout defaults to 20s, and all the rest default to 120s. Also, `lib/pengine/common.c` states that...

LVM-activate: Improve return codes and handling of missing PVs

6

`OCF_ERR_ARGS` and `OCF_ERR_CONFIGURED` were used in inappropriate ways that led to starts being disallowed in the wrong places. This pull attempts to correct that. `lvm_status()` and `lvm_stop()` weren't designed to...

Medium: exportfs: Use canonical hostname for monitor op

3

#### Issue If the hostname specified in `clientspec` does not match the canonical hostname, the monitor operation fails even though the export exists. This is caused by the exportfs command's...

I'm opening this issue to capture @mike-19's request in PR comments: https://github.com/ClusterLabs/resource-agents/pull/1604#issuecomment-758420251

Fix: tools: crm_mon --daemonize should update when disconnected

6

With `crm_mon --daemonize`, the output will continue to show the last known status after the cluster is stopped on the local node. It should go back to something like `"Cluster...