Pacemaker 2.0.3 - Final
kgaillot
released this
25 Nov 22:57
·
1264 commits
to 2.0
since this release
Known regressions introduced in this release
- The -T/--tag option to stonith_admin stopped working (fixed in 2.1.3)
- crm_mon can crash when running in daemon mode with CGI output (fixed in 2.1.0)
- HTTP headers could be incorrectly added when crm_mon is run in daemon mode (fixed in 2.0.5)
- Expected score of ping attributes are incorrectly omitted from crm_mon XML output (fixed in 2.0.5)
Features added since Pacemaker-2.0.2
- controller: new 'fence-reaction' cluster option specifies whether local node should 'stop' or 'panic' if notified of own fencing
- controller: more cluster properties support ISO 8601 time specifications
- controller: calculate cluster recheck interval dynamically when possible
- Pacemaker Remote: allow file for environment variables when used in bundle
- Pacemaker Remote: allow configurable listen address and TLS priorities
- tools: crm_mon now supports standard --output-as/--output-to options
- tools: crm_mon HTML output supports user-defined CSS stylesheet
- tools: stonith_admin supports HTML output in addition to text and XML
- tools: crm_simulate supports --repeat option to repeat profiling tests
- tools: new pcmk_simtimes tool compares crm_simulate profiling output
- agents: SysInfo supports K, T, and P units in addition to Kb and G
Changes since Pacemaker-2.0.2
- fencer: do not block concurrent fencing actions on a device (regression since 2.0.2)
- all: avoid Year 2038 issues
- all: allow ISO 8601 strings of form "T "
- rpm: pacemaker-cts package now explicitly requires pacemaker-cli
- controller: set timeout on scheduler responses to avoid infinite wait
- controller: confirm cancel of failed monitors, to avoid transition timeout
- executor: let controller cancel monitors, to avoid transition timeout
- executor: return error for stonith probes if stonith connection was lost
- fencer: ensure concurrent fencing commands always get triggered to execute
- fencer: fail pending actions and re-sync history after crash and restart
- fencer: don't let command with long delay block other pending commands
- fencer: allow functioning even if CIB updates arrive unceasingly
- scheduler: wait for probe actions to complete to prevent unnecessary restart/re-promote of dependent resources
- scheduler: avoid invalid transition when guest node host is not fenceable
- scheduler: properly detect dangling migrations, to avoid restart loop
- scheduler: avoid scheduling actions on remote node that is shutting down
- scheduler: avoid delay in recovery of failed remote connections
- scheduler: clarify action failure log messages by including failure time
- scheduler: calculate secure digests for unfencing, for replaying saved CIBs
- libcrmcommon: avoid possible use-of-NULL when applying XML diffs
- libcrmcommon: correctly apply XML diffs with multiple move/create changes
- libcrmcommon: return error when applying XML diffs with unknown operations
- tools: avoid duplicate lines between nodes in crm_simulate dot graph
- tools: count disabled/blocked resources correctly in crm_mon/crm_simulate
- tools: crm_mon --interval now accepts ISO 8601 and has correct help
- tools: organize crm_mon text output with list headings, indents, bullets
- tools: crm_report: fail if tar is not available
- tools: crm_report: correct argument parsing
- tools: crm_report: don't ignore log if unrelated file is too large
- tools: stonith_admin --list-targets should show what fencer would use
- agents: calculate #health_disk correctly in SysInfo
- agents: handle run-as-user properly in ClusterMon