{"push_id":545465757,"size":1,"distinct_size":1,"ref":"refs/heads/fix-hapolicy","head":"f77afbf8c5635a91680593a7290d432e0e3b55d5","before":"b54cffc3bd7f14c6184d6c36ad50b1369d5da6e3","commits":[{"sha":"f77afbf8c5635a91680593a7290d432e0e3b55d5","author":{"email":"fce325d9bea9824893a19b950fc06b32172551f5@redhat.com","name":"John Eckersberg"},"message":"BZ #1168755 - rabbitmqctl failure while setting HA policy\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1168755\n\nThe policies are set in the clustered database and replicated across\nthe cluster.  As such, it really only needs to be set on the first\nnode, and then it will replicate to the others when they join the\ncluster.  I think something like the following happens:\n\n- First node starts, sets HA policy\n\n- Second node \"starts\".  My suspicion is that there is probably some\n  cluster state sync happening in the background after the systemd\n  unit succeeds.\n\n- Second node attempts to set HA policy (unnecessarily) but cannot\n  connect to local rabbit node due to race condition with clustering\n  and state synchronization.\n\n- Explosions and sadness, puppet errors.\n\nThis change declares the exec only for the first node, so additional\ncluster members will just inherit the policy from the cluster state.","distinct":true,"url":"https://api.github.com/repos/jeckersb/astapor/commits/f77afbf8c5635a91680593a7290d432e0e3b55d5"}]}