Issue is described in clusterlabs mailing list - http://oss.clusterlabs.org/pipermail/pacemaker/2015-February/023479.html . So, issue is may be appeared in case if we have automation scripts what produces high payload on CIB and it may be critical for our customers who are basing their own solution under the vanilla fuel releases. As it was described in mailing list the first version what was not affected is '2.1.2' (2.1.0 our current version) This version contains several patches to prevent such kind of fails: https://github.com/ClusterLabs/crmsh/commit/7a4a34d91da08cb0c0fd7a1de26f77d798397723 https://github.com/ClusterLabs/crmsh/commit/c0081b23920900cd2c97e47bd5a3d38cbe3a1b51
So, it's necessary to switch to 2.1.2 crmsh version in our 7/8 releases.
Issue is described in clusterlabs mailing list - http:// oss.clusterlabs .org/pipermail/ pacemaker/ 2015-February/ 023479. html . So, issue is may be appeared in case if we have automation scripts what produces high payload on CIB and it may be critical for our customers who are basing their own solution under the vanilla fuel releases. /github. com/ClusterLabs /crmsh/ commit/ 7a4a34d91da08cb 0c0fd7a1de26f77 d798397723 /github. com/ClusterLabs /crmsh/ commit/ c0081b23920900c d2c97e47bd5a3d3 8cbe3a1b51
As it was described in mailing list the first version what was not affected is '2.1.2' (2.1.0 our current version)
This version contains several patches to prevent such kind of fails:
https:/
https:/
So, it's necessary to switch to 2.1.2 crmsh version in our 7/8 releases.