{"push_id":700400523,"size":1,"distinct_size":1,"ref":"refs/heads/release-3.7","head":"84479bfa28f91c993b4e4a1f0f259a3ae1576791","before":"c4d4d2247b3aeb96e37a05aeb0f73cec54360094","commits":[{"sha":"84479bfa28f91c993b4e4a1f0f259a3ae1576791","author":{"email":"8666478417b23a05777ccdb0da96ce6896073c19@redhat.com","name":"Kotresh HR"},"message":"glusterd: Fix snapshot of a volume with geo-rep\n\nProblem:\n    Snapshot fails for a volume configured with geo-rep\n    if geo-rep is created with root user with the following\n    syntax.\n    gluster vol geo-rep <master_vol> root@<slave_host>::<slave_vol>\n\n    It works fine if created with following syntax.\n    gluster vol geo-rep <master_vol> <slave_host>::<slave_vol>\n\nCause:\n    Geo-rep maintains persistent dictionary of slave associated\n    with master volume. The dictionary saves the slave info\n    along with 'root@' as sent from cli.\n    Snapshot while constructing the working dir path to copy\n    configuration files, constructs using this dictionary.\n    But the actual working dir is created with out considering\n    'root@'. Hence the issue.\n\nFix:\n    Fix is done at two layers.\n    1. Parse and negelect 'root@' in cli itself.\n    2. For existing geo-rep sessions and upgrade scenarios,\n       parse and neglect 'root@' in snapshot code as well.\n\nBUG: 1233056\nChange-Id: Ic666e43a1c4ac2f3f0fb957caa77770e1eee4129\nSigned-off-by: Kotresh HR <khiremat@redhat.com>\nReviewed-on: http://review.gluster.org/11233\nReviewed-on: http://review.gluster.org/11310\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>","distinct":true,"url":"https://api.github.com/repos/gluster/glusterfs/commits/84479bfa28f91c993b4e4a1f0f259a3ae1576791"}]}