Pacemaker 1.1.18 - Final

Release info

• Changesets: 644
• Diff: 167 files changed, 9753 insertions(+), 5596 deletions(-)

Known regressions introduced in this release

• Agent meta-data is not always refreshed after a resource start, in case the agent was updated (fixed in 2.1.0)
• A resource may have unnecessary downtime when it needs to be moved to a Pacemaker Remote node that fails to come up (fixed in 2.0.1)
• attrd's node name might not be broadcast at start-up (fixed in 2.0.0)
• Unfencing might be incorrectly scheduled after probing or starting fence devices (fixed in 2.0.0)
• crm_simulate -sL does not show master scores (fixed in 2.0.0)
• crm_master does not work without explicit --lifetime (fixed in 2.0.0)

Features added since Pacemaker-1.1.17

• warnings are now logged when using legacy syntax to be removed in 2.0
• agents: ifspeed agent is now installed when building
• agents: ifspeed agent can optionally detect interface name from IP address
• alerts: support alert filters
• alerts: experimental support for alerts for node attribute changes
• crmd,pengine: support unfencing of remote nodes
• pengine: bundles now support all constraint types
• pengine: bundles now support rkt containers
• pengine: bundles support new container-attribute-target parameter
• pengine,tools: logs and crm_mon show why resources changed state
• stonith-ng: support new fencing resource parameter pcmk_delay_base
• tools: new crm_resource option --why explains why resources are stopped

Changes since Pacemaker-1.1.17

• many documentation improvements
• agents: ifspeed properly calculates speed of hfi1 interfaces
• agents: ClusterMon now interprets "update" less than 1000 as seconds
• attrd: don't lose attributes set between attrd start-up and cluster join
• attrd: fix multiple minor memory leaks
• crmd: correctly record that unfencing is complete
• crmd: error more quickly if remote start fails due to missing key
• lrmd: remote resource operations return immediate error if key setup fails
• lrmd: allow pre-1.1.15 cluster nodes to connect to current Pacemaker Remote
• pengine: guest nodes are now probed like other nodes
• pengine: probe remote nodes for guest node resources
• pengine: do not probe guest/bundle connections until guest/bundle is active
• pengine: allow resources to stop prior to probes completing
• pengine: bundles wait only for other containers on same node to be probed
• pengine: have bundles log to stderr so 'docker logs'/'journalctl -M' works
• pengine: only pass requests for promote/demote flags onto the bundle's child
• pengine: do not map ports into Docker container when net=host is specified
• pengine: allow resources inside bundles to receive clone notifications
• pengine: default to non-interleaved bundle ordering for safety
• pengine: ensure bundle nodes and child resources are correctly cleaned up
• pengine: prevent graph loops when fencing the host underneath a bundle
• pengine: fix multiple memory issues (use-after-free, use-of-NULL) with bundles
• pengine: resources in bundles respect failcounts
• pengine: ensure nested container connections run on the same host
• pengine: ensure unrecoverable remote nodes are fenced even with no resources
• pengine: handle resource migrating behind a migrating remote connection
• pengine: don't prefer to keep unique instances on same node
• pengine: exclude exclusive resources and nodes from symmetric default score
• pengine: if ignoring failure, also ignore migration-threshold
• pengine: restore the ability to send the transition graph via the disk if it gets too big
• pengine: validate no-quorum-policy=suicide correctly
• pengine: avoid crash when alerts section has comments
• pengine: detect permanent master scores at start-up
• pengine: do not re-add a node's default score for each location constraint
• pengine: make sure calculated resource scores are consistent on different architectures
• pengine: retrigger unfencing for changed device parameters only when necessary
• pengine: don't schedule reload and restart in same transition (CLBZ#5309, regression introduced in 1.1.15)
• stonith-ng: make fencing-device reappear properly after reenabling
• stonith-ng: include pcmk_on_action in meta-data so 'on' can be overridden
• tools: allow crm_report to work with no log files specified
• tools: fix use-after-free in crm_diff introduced in 1.1.17
• tools: allow crm_resource to operate on anonymous clones in unknown states
• tools: crm_resource --cleanup on appropriate nodes if we don't know state of resource
• tools: prevent disconnection from crmd during crm_resource --cleanup
• tools: improve messages for crm_resource --force-* options
• tools: crm_mon: avoid infinite process spawning if -E script can't be run
• tools: crm_mon: don't show previous exit-reason for failed action with none
• libcrmservice: list systemd unit files, not only active units (CLBZ#5299)
• libcrmservice: parse long description correctly for LSB meta-data