{"push_id":2670810420,"size":1,"distinct_size":1,"ref":"refs/heads/reset-rabbit-during-upgrade","head":"1b64349948b05f1ccc0cfac90583f525a753f537","before":"ef5210832d79f45ff00df1e9177cb148a927b14a","commits":[{"sha":"1b64349948b05f1ccc0cfac90583f525a753f537","author":{"name":"Jacek Tomasiak","email":"e09ceaaec8e6e5d02a5e2a59b166644e946f988c@gmail.com"},"message":"upgrade: Reset RabbitMQ nodes during upgrade (bsc#1098179)\n\nRabbitMQ requires re-start of cluster to be started from former master\nnode or multiple resets are needed before sync status is reached.\nIt is easier to just reset the nodes before stopping the cluster and\nstart from scratch with new one after upgrade.\n\nThis should solve the problem when someone tries to use not-yet-ready\nRabbitMQ cluster immediately after controllers upgrade (e.g. doing\nlive-migration of computes via Nova API).","distinct":true,"url":"https://api.github.com/repos/skazi0/crowbar-core/commits/1b64349948b05f1ccc0cfac90583f525a753f537"}]}
{"actor":{"display_login":"skazi0"}}