On 3/4/19 8:09 AM, Hari Gowtham wrote: > On Mon, Mar 4, 2019 at 6:18 PM Shyam Ranganathan <[email protected]> wrote: >> >> On 3/4/19 7:29 AM, Amar Tumballi Suryanarayan wrote: >>> Thanks for testing this Hari. >>> >>> On Mon, Mar 4, 2019 at 5:42 PM Hari Gowtham <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi, >>> >>> With the patch https://review.gluster.org/#/c/glusterfs/+/21838/ the >>> upgrade from 3.12 to 6, 4.1 to 6 and 5 to 6 is broken. >>> >>> The above patch is available in release 6 and has been back-ported >>> to 4.1 and 5. >>> Though there isn't any release made with this patch on 4.1 and 5, if >>> made there are a number of scenarios that will fail. Few are mentioned >>> below: >>> >>> >>> Considering there is no release with this patch in, lets not consider >>> backporting at all. > > It has been back-ported to 4 and 5 already. > Regarding 5 we have decided to revert and make the release. > Are we going to revert the patch for 4 or wait for the fix?
Release-4.1 next minor release is slated for week of 20th March, 2019. Hence, we have time to get the fix in place, but before that I would revert it anyway, so that tracking need not bother with possible late arrival of the fix. > >> >> Current 5.4 release (yet to be announced and released on the CentOS SIG >> (as testing is pending) *has* the fix. We need to revert it and rebuild >> 5.4, so that we can make the 5.4 release (without the fix). >> >> Hari/Sanju are you folks already on it? > > Yes, Sanju is working on the patch. Thank you! > >> >> Shyam > > _______________________________________________ maintainers mailing list [email protected] https://lists.gluster.org/mailman/listinfo/maintainers
