{"push_id":910844937,"size":3,"distinct_size":0,"ref":"refs/heads/master-tag","head":"f61954fa6120c7be5dd1e9dc0ac2287d0be0f0dc","before":"44b4ef253864970072d3d92c1ddc476ac0992266","commits":[{"sha":"ed7dd778caccafb9d86b70a8b17f01c66b547bfb","author":{"email":"5ee0edb9e2229c0838f1959779f1949031de0123@bishnet.net","name":"Tim Bishop"},"message":"Log the crm output when retrying.\n\nI've noticed that with an empty Pacemaker configuration that Puppet\ngets stuck in a loop waiting forever for it to become ready. This\nturns out to be because dc-version isn't set. By logging the output\nof the command we get some clue about what's happening.","distinct":false,"url":"https://api.github.com/repos/rdo-puppet-modules/puppetlabs-corosync/commits/ed7dd778caccafb9d86b70a8b17f01c66b547bfb"},{"sha":"54f558f80844c655b042f69274d4c613d52cd3e0","author":{"email":"5ee0edb9e2229c0838f1959779f1949031de0123@bishnet.net","name":"Tim Bishop"},"message":"Log the update being loaded by crm.\n\nSometimes updates fail to apply and it's not clear why. I'm not\nsure how to get the output (stderr?) out of the crm exec, but this\nchange is a step nearer to finding out what's going on. By logging\nthe update being run it's fairly easy to replicate it on the command\nline and see the error message.","distinct":false,"url":"https://api.github.com/repos/rdo-puppet-modules/puppetlabs-corosync/commits/54f558f80844c655b042f69274d4c613d52cd3e0"},{"sha":"f61954fa6120c7be5dd1e9dc0ac2287d0be0f0dc","author":{"email":"5ee0edb9e2229c0838f1959779f1949031de0123@bastelfreak.de","name":"Tim Meusel"},"message":"Merge pull request #177 from tdb/log-crm-updates\n\nLog crm updates as debug level","distinct":false,"url":"https://api.github.com/repos/rdo-puppet-modules/puppetlabs-corosync/commits/f61954fa6120c7be5dd1e9dc0ac2287d0be0f0dc"}]}