[Bugs] [Bug 1687051] gluster volume heal failed when online upgrading from 3.12 to 5.x and when rolling back online upgrade from 4.1.4 to 3.12.15

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 22 06:13:07 UTC 2019


--- Comment #60 from Sanju <srakonde at redhat.com> ---

Sorry for the delay in response.
According to https://bugzilla.redhat.com/show_bug.cgi?id=1676812 heal command
"Launching heal operation to perform index self heal on volume <volname> has
been unsuccessful:
Commit failed on <ip_addr>. Please check log file for details"

when any of the brick in the volume is down. But in background heal operation
will continue to happen. Here, the error message is misleading. I request you
to take a look at https://review.gluster.org/22209 where we tried to change
this message but retained ourselves from doing it based on the discussions over
the patch.

I believe in your setup also, if you check the files in bricks they will be
healing. and, we never tested the rollback scenario's in our testing. But
everything should be fine after rollback.


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

More information about the Bugs mailing list