- Handle large timeouts correctly in crm_resource --wait
- Do not try to connect to subdaemons before they're respawned
- Don't evict IPC clients as long as they're still processing messages
- Don't overwhelm the FSA queue with repeated CIB queries
- Resolves: RHEL-45869
- Resolves: RHEL-87484
- Resolves: RHEL-114894
- Use async communication to establish TLS connections
- Fix regression in adding alerts to CIB
- Fix a crash in command line tools when stderr is closed
- Resolves: RHEL-61382
- Resolves: RHEL-34276
- Resolves: RHEL-55458
- Resolves: RHEL-59043
- Add ability to immediately shutdown system with PCMK_panic_action=
- Fix a memory leak in the attribute daemon
- Add ability to list options and parameters as parseable metadata
- crm_verify now reports invalid fence level indexes
- Fix an error in node ID handling in `crm_node -i`
- Fix regression in attrd_updater output
- Resolves: RHEL-39057
- Resolves: RHEL-40117
- Resolves: RHEL-23401
- Resolves: RHEL-2996
- Resolves: RHEL-47249
- Resolves: RHEL-45935
The pacemaker-libs-devel package contains
/usr/include/pacemaker/crm_config.h which defines BUILD_VERSION. This
macro is set to the git commit ID that was used to build this package.
In previous releases, we had a bug in configure.ac that caused us to
incorrectly fail to find git, resulting in using the fallback of the
source tree directory name. This is something like pacemaker-1234abcd,
which is the same on all builders.
However, 2.1.7 includes a fixed configure.ac that can now find the git
binary which means we now use the latest git commit ID. Unfortunately,
this varies from builder to builder even for the same release. This is
because the first steps in package building are running "git commit" to
initialize a repo, and then running "git am" to apply all the patches.
Creating the repo means it will get a different commit ID every time,
which means the applied patches will have a different parent, giving
them different commit IDs.
The end result of this is that each builder sees its own distinct commit
ID, and therefore each arch has its own BUILD_VERSION. This means the
x86_64 and i686 packages now differ, introducing a file conflict, which
means rpm will refuse to upgrade.
The fix is to simply remove the automatically created git repo after we
are done with it, causing configure.ac to use the directory name
fallback.
- Resolves: RHEL-28999
- Fix documentation for Pacemaker Remote schema transfers
- Do not check CIB feature set version when CIB_file is set
- Consolidate attrd cache handling
- Avoid duplicating option metadata across daemons
- Related: RHEL-7665
- Related: RHEL-13216
- Resolves: RHEL-7702
- Use systemd-sysusers to create user/group
- Pacemaker Remote nodes can validate against later schema versions
- Related: RHEL-17225
- Resolves: RHEL-7665
- Additional fixes for SIGABRT during pacemaker-fenced shutdown
- Backport fix for attrd_updater -QA not displaying all nodes
- Related: rhbz2166967
- Resolves: rhbz2169829
- Resolves: rhbz2089353
I'm jumping from specversion 3 to 5 to restore parity with RHEL 8.7, otherwise
users of both might get confused about whether they have all fixes.
Also correct some broken URLs in the spec file
- Unable to show metadata for "service" agents with "@" and "." in the name
- Resource ocf:pacemaker:attribute does not comply with the OCF 1.1 standard
- Pacemaker does not convert & to & when generating metadata for non-ocf agents
- Resolves: rhbz2045110
- Resolves: rhbz2049720
- Resolves: rhbz2050259
- Resolves: rhbz2072108
- Correctly get metadata for systemd agent names that end in '@'
- Use correct OCF 1.1 syntax in ocf:pacemaker:Stateful meta-data
- Fix regression in displayed times in crm_mon's fence history
- Resolves: rhbz2032031
- Resolves: rhbz2032032
- Resolves: rhbz2031765
- Fix watchdog agent version information
- Ensure transient attributes are cleared when multiple nodes are lost
- Resolves: rhbz1443666
- Resolves: rhbz1986998
- Avoid selecting wrong device when dynamic-list fencing is used with host map
- Show better error messages in crm_resource with invalid resource types
- Do not schedule probes of unmanaged resources on pending nodes
- Fix regressions in crm_attribute and crm_master argument handling
- Resolves: rhbz1978013
- Resolves: rhbz1983196
- Resolves: rhbz1983197
- Resolves: rhbz1984130
