[Bugs] [Bug 1473026] replace-brick failure leaves glusterd in inconsistent state

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1473026

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ravishankar at redhat.com
          Component|replicate                   |glusterd



--- Comment #2 from Ravishankar N <ravishankar at redhat.com> ---
Code snippet in case if replicate volume:

glusterd_op_perform_replace_brick()
{

   1. glusterd_op_perform_remove_brick();
   2. ret=glusterd_handle_replicate_brick_ops();
      if (ret) {
       goto out;
       }
   3. glusterd_create_volfiles_and_notify_services();

}

With the test mentioned in the bug description, ret value is non-zero in
step-2. So glusterd would need to roll-back the changes it did before step-2.
I.e. it needs to undo the remove-brick done in step-1.

Changing the component to glusterd based on the above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.