[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
Fri Mar 15 04:56:46 UTC 2019


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

Karthik U S <ksubrahm at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|ksubrahm at redhat.com         |srakonde at redhat.com



--- Comment #23 from Karthik U S <ksubrahm at redhat.com> ---
Hi,

Sorry for the delay.
In the first case of conversion from 3.12.15 to 5.3, the bricks on the upgraded
nodes failed to come up. The heal command will fail if any of the bricks are
not available or down.
In the second case of conversion from 4.1.4 to 3.12.15 even though we have all
the bricks and shd up and running I can see some errors in the glusterd logs
during the commit phase of the heal command.

We need to check from glusterd side why this is happening. Sanju are you aware
of any such cases? Can you debug this further to see why the brick is failing
to come up and why the heal commit fails?

Regards,
Karthik

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


More information about the Bugs mailing list