{"push_id":676701904,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"638ab3b972dd467b11c59535cfbe12bd843483d9","before":"05b59b7c9279222de734295535d86f53dd3d4225","commits":[{"sha":"e8e777a55b6d31e197c97cc6380c2c0e49927b0a","author":{"email":"0b23cd1e586d5f091fecb3391314c2b9ec1fd641@mirantis.com","name":"Bogdan Dobrelya"},"message":"Check if the rabbitmqctl command is responding\n\nW/o this fix, rabbitmqctl sometimes may hang failing\nmany commands. This is a problem as it brings the rabbit node\nto unresponsive and broken state. This also may affect\nentire cluster operations, for example, when the failed command is\nthe forget_cluster_node.\n\nThe solution is to check for the cases when the command rabbitmqctl\nlist_channels timed out and killed or termintated with exit codes\n137 or 124 and return generic error.\nThere is also related confusing error message \"get_status() returns generic\nerror\" may be logged when the rabbit node is running out of the cluster\nand fixed as well.\n\nCloses-bug: #1459173\n\nChange-Id: Ia52fc5f2ab7adb36252a7194f9209ab87ce487de\nSigned-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>","distinct":true,"url":"https://api.github.com/repos/stackforge/fuel-library/commits/e8e777a55b6d31e197c97cc6380c2c0e49927b0a"},{"sha":"638ab3b972dd467b11c59535cfbe12bd843483d9","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Check if the rabbitmqctl command is responding\"","distinct":true,"url":"https://api.github.com/repos/stackforge/fuel-library/commits/638ab3b972dd467b11c59535cfbe12bd843483d9"}]}