File _patchinfo of Package patchinfo.9287
<patchinfo incident="9287"> <issue tracker="bnc" id="918839">ClusterMon / CRM_notify_node shows node_id instead node_name as in SLES11</issue> <issue tracker="bnc" id="950551">frequent logging notice: update_validation: pacemaker-x.y-style configuration</issue> <issue tracker="bnc" id="948989">Pacemaker doesn't wait for systemd resource stop</issue> <issue tracker="bnc" id="970733">pcmk_delay_max or start-delay with external/vcenter</issue> <issue tracker="bnc" id="976271">ocf_pacemaker_ping should be using fping6 for IPv6 addresses</issue> <issue tracker="bnc" id="938545">Fencing of a complete site takes a long time</issue> <issue tracker="bnc" id="956626">Apache cluster resource floods system log with systemd errors</issue> <issue tracker="bnc" id="1053463">pacemaker remote resource doesn't start</issue> <issue tracker="bnc" id="993835">L3-Question: systemd Resources take triple the time in SP0 than in SP1</issue> <issue tracker="bnc" id="921102">"Too many failures to fence" does not recover as expected</issue> <issue tracker="bnc" id="950450">Resource monitor failcount increasing after migration.</issue> <issue tracker="bnc" id="977800">pengine does not organize order of actions for master resources in anti-colocations</issue> <issue tracker="bnc" id="914761">repeating monitor started also on the wrong node after migrate_to failed</issue> <issue tracker="bnc" id="909286">crm_mon does not work with "event notification" anymore</issue> <issue tracker="bnc" id="931271">LRMD fails on monitor under high load, causing failover</issue> <issue tracker="bnc" id="977675">order symmetrical=false, rsc not started after migration</issue> <issue tracker="bnc" id="977258">incorrect timeout of pacemaker RA start operation when start-delay is configured</issue> <issue tracker="bnc" id="1042054">Cluster configuration with ACL causes false Permission Denied on a non-DC node</issue> <issue tracker="bnc" id="917625">Node fails to join the cluster with error: handle_request message</issue> <issue tracker="bnc" id="956500">dbus: Rejected send message from crmd</issue> <issue tracker="bnc" id="972187">monitor failure does not always restart resource</issue> <issue tracker="bnc" id="946224">verify_cib_status.sh: ERROR: CIB is not in sync</issue> <issue tracker="bnc" id="943319">systemd resource monitor flooding /var/log/pacemaker.log</issue> <issue tracker="bnc" id="949267">Message every second in log - Forwarding noop operation for section 'all'</issue> <issue tracker="bnc" id="940992">Confusing recommendations on the suggested size for the PCMK_ipc_buffer</issue> <category>recommended</category> <rating>moderate</rating> <packager>aburlakov</packager> <description>This update for pacemaker fixes the following issues: crm_mon - Repair notification delivery when the v2 patch format is in use. (bsc#909286) - Fill CRM_notify_node in traps with node's uname. (bsc#918839) crmd - Cached copies of transient attributes cease to be valid once a node leaves the membership. (bsc#917625) - Add "on_node" attribute for *_last_failure_0 lrm resource operations. (bsc#918839) - Reset stonith failcount to recover transitioner when the node rejoins. (bsc#921102) - All peers need to track node shutdown requests. (bsc#917625) - Prevent doubled fail count for same failure. (bsc#950450) - Take start-delay into account for the timeout of the action timer. (bsc#977258) dbus - Use operation timeout for dbus reply timeout (bsc#931271) and unref reply when they are done. (bsc#931271) systemd - Reconnect to System DBus if the connection is closed. (bsc#931271) - Kindly ask dbus NOT to kill the process if the dbus connection fails. (bsc#931271) - Perform actions asynchronously. (bsc#956500, bsc#993835) - Correctly handle long running stop actions. (bsc#948989) services - Reduce severity of noisy log messages. (bsc#943319) cib - Check if the configuration changes with cib_config_changed() only for v1 diffs. (bsc#946224) - Downgrade the log message on forwarding CRM_OP_NOOP. (bsc#949267) - Broadcasts of cib changes should always pass ACLs check. (bsc#1042054) lrmd - Finalize all pending and recurring operations when cleaning up a resource. (bsc#950450) - Hint to child processes that using sd_notify is not required. (bsc#956626) - Make sure the operation of a remote resource returns if setup of the key fails. (bsc#1053463) xml - Reduce severity of xslt upgrade and noisy log messages. (bsc#950551, bsc#950551) pengine - Consider resource failed if any of the configured monitor operations failed. (bsc#972187) - Do not reschedule monitors that are no longer needed while resource definitions have changed. (bsc#914761) - Resolve memory leaks. (bsc#914761) - Reschedule specific monitors when resource definitions have changed. (bsc#914761) - lf#2560/lf#2588 - Correctly set the environment variable "OCF_RESKEY_CRM_meta_timeout" when "start-delay" is configured. (bsc#977258) - Respect asymmetrical ordering when trying to move resources. (bsc#977675) - Organize order of actions for master resources in anti-colocations. (bsc#977800) - Ensure fencing of the DC precedes the STONITH_DONE operation. (bsc#938545) - Support concurrent fencing. (bsc#938545) fencing - Support concurrent fencing actions on each device. (bsc#938545) - Functionize adding and removing active pids of device. (bsc#938545) - Correctly track active stonith actions. (bsc#938545) - cl#5134 - Support random fencing delay to avoid double fencing. (bsc#970733) ipc - Correctly compare values for the size of ipc buffer and prevent suggesting a negative value when it is insufficient. (bsc#940992) - Fix output formats. (bsc#940992) - Do not constantly increase suggested size for PCMK_ipc_buffer every time we find it's insufficient. (bsc#940992) ping resource - Use fping6 for IPv6 hosts. (bsc#976271) </description> <summary>Recommended update for pacemaker</summary> </patchinfo>