File _patchinfo of Package patchinfo.12004

<patchinfo incident="12004">
  <issue tracker="bnc" id="1137038">L3-Question: rsc_azure-events resource causing errors in /var/log/messages</issue>
  <issue tracker="bnc" id="1133337">ctdb naming breaks resource-agents (HA) parsing</issue>
  <issue tracker="bnc" id="1131793">L3: Pacemaker SST databases to /dev/null</issue>
  <issue tracker="bnc" id="1125138">Patches for aws-vpc-move-ip agent to support multi routing tables are missing</issue>
  <issue tracker="bnc" id="1114855">[Build 85.6] openQA test fails in check_after_boot: vg_cluster_md configured with lvmlockd fails to start after fence</issue>
  <issue tracker="bnc" id="1140874">Include the latest aws-vpc-route53 bug fixes and improvements from upstream.</issue>
  <issue tracker="bnc" id="1133962">aws-vpc-move-ip - defect making update of route table fail in case VM has multiple network interfaces</issue>
  <issue tracker="bnc" id="1137231">azure-events Resource Agent does not start with the error:  "ERROR: a bytes-like object is required, not 'str'"</issue>
  <packager>varkoly</packager>
  <rating>moderate</rating>
  <category>recommended</category>
  <summary>Recommended update for resource-agents</summary>
  <description>This update for resource-agents fixes the following issues:

- The version of resource-agents was updated to 4.3.018.a7fb5035 and has addressed a couple
  of bugs. Some of the bugs are:

  * L3: Pacemaker SST databases to /dev/null (bsc#1131793) [waiting for a customer friendly description]
  * azure-events: changed the default log level to 'warning' (bsc#1137038, bsc#1137231)
  * CTDB: Fixes the version string with vendor trailer comparison (bsc#1133337)
  * Fixes an issue where aws-vpc-move-ip failed when a VM has more than one network interface (bsc#1133962)

Please refer to this rpm's changelog to obtain a full list of all changes.
</description>
</patchinfo>