{"push_id":1253694797,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"dd8d93f24a320805f1f67760b2d3266555acf674","before":"a42644198431b37c9fcad2b1ff4f98b4df16c91e","commits":[{"sha":"dd8d93f24a320805f1f67760b2d3266555acf674","author":{"name":"Samikshan Bairagya","email":"074ecba8189aac1c20caadac093539d9820b8605@gmail.com"},"message":"glusterd: Fix volume restart issue upon glusterd restart\n\nhttp://review.gluster.org/#/c/14758/ introduces a check in\nglusterd_restart_bricks that makes sure that if server quorum is\nenabled and if the glusterd instance has been restarted, the bricks\ndo not get started. This prevents bricks which have been brought\ndown purposely, say for maintainence, from getting started\nupon a glusterd restart. However this change introduced regression\nfor a situation that involves multiple volumes. The bricks from\nthe first volume get started, but then for the subsequent volumes\nthe bricks do not get started. This patch fixes that by setting\nthe value of conf->restart_done to _gf_true only after bricks are\nstarted correctly for all volumes.\n\nChange-Id: I2c685b43207df2a583ca890ec54dcccf109d22c3\nBUG: 1367478\nSigned-off-by: Samikshan Bairagya <samikshan@gmail.com>\nReviewed-on: http://review.gluster.org/15183\nSmoke: Gluster Build System <jenkins@build.gluster.org>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.org>\nReviewed-by: Atin Mukherjee <amukherj@redhat.com>","distinct":true,"url":"https://api.github.com/repos/gluster/glusterfs/commits/dd8d93f24a320805f1f67760b2d3266555acf674"}]}
{"actor":{"display_login":"mscherer"}}