{"push_id":1956052126,"size":3,"distinct_size":3,"ref":"refs/heads/pr-1104","head":"61f61d725bda46c43d6093e11e0a3c977207cd6f","before":"c4b9b1d9b141431910ec2ec2ccab95476f11fd2c","commits":[{"sha":"72625394ecbcab66539d7e1a10f7a77ff3cd766e","author":{"name":"Itxaka","email":"295f01a40c9e830b71c587ca0511d155fb4789aa@suse.com"},"message":"rabbit: More robust check for rabbit\n\nThe original method used for checking if rabbit is up was not reliable\nand it frozen several times while waiting for the PID. The new method\nprovides a much more reliable way to find out if rabbit is up and\nrunning.","distinct":true,"url":"https://api.github.com/repos/matelakat/crowbar-openstack/commits/72625394ecbcab66539d7e1a10f7a77ff3cd766e"},{"sha":"207313b9b758d4f0d9c6e569ca90a36f5c3c4a35","author":{"name":"Itxaka","email":"295f01a40c9e830b71c587ca0511d155fb4789aa@suse.com"},"message":"rabbit: dont let the template changes restart if in cluster mode\n\nAs the restart for a Pacemaker service runs only for the resource\nin the current node, and the master node get_monitor returns an 8\nas exit code (to indicate that its the master) we are forcing a\nstop and start of the resource only in the slave, which can lead\nto pacemaker not syncing properly between the nodes.\n\nInstead, just do not allow the configuration at the start of the\ncommon recipe to queue a restart action, as any changes to the\ntemplates are done before we start the rabbit service, its not\nrequired","distinct":true,"url":"https://api.github.com/repos/matelakat/crowbar-openstack/commits/207313b9b758d4f0d9c6e569ca90a36f5c3c4a35"},{"sha":"61f61d725bda46c43d6093e11e0a3c977207cd6f","author":{"name":"Mate Lakat","email":"904278e2bbacbd1cd8c8df3579145ca3dc9c8114@suse.com"},"message":"Disable ceilometer middleware when using durable queues\n\nCeilometer middleware cannot be used with durable queues as it does not\nhave the durable_queues configuration option. Therefore if swift proxy\ncomes up first it might create the queues wrongly, leading all other\ncomponents being unable to connect to notifications.info.\n\nError messages like this can indicate the error:\n\n```\nFailed to publish message to topic 'nova': Queue.declare: (406)\nPRECONDITION_FAILED - inequivalent arg 'durable' for queue\n'notifications.info' in vhost '/nova': received 'true' but current is\n'false'\n```","distinct":true,"url":"https://api.github.com/repos/matelakat/crowbar-openstack/commits/61f61d725bda46c43d6093e11e0a3c977207cd6f"}]}
{"actor":{"display_login":"matelakat"}}