On 02/13/2018 12:35 AM, Atin Mukherjee wrote: > > > On Tue, Feb 13, 2018 at 10:43 AM, Jiffin Tony Thottan > <jthottan@xxxxxxxxxx <mailto:jthottan@xxxxxxxxxx>> wrote: > > Since the change was there from 3.10 onwards, only upgrade from > eoled version to stable will break right? > > I didn't notice anyone complaining about the issue in community till > now. > > > If any one upgrades the cluster from < 3.10 to >= 3.10, it's a genuine > problem as per my code reading. So I tested 3.9 -> 3.10 -> 3.12 -> 3.13 upgrades (during release times). Actually n-1 to n where 'n' is the current release. What I do *not* test is every option that can be enabled, and the resultant upgrade scenario. (which I believe we should do) What is the shortest way to at *least* test, - added options - changed options for a release? > > > -- > > Jiffin > > > > On Tuesday 13 February 2018 08:21 AM, Hari Gowtham wrote: > > I'm working on it. > > On Tue, Feb 13, 2018 at 8:11 AM, Atin Mukherjee > <amukherj@xxxxxxxxxx <mailto:amukherj@xxxxxxxxxx>> wrote: > > FYI.. We need to backport > https://review.gluster.org/#/c/19552 > <https://review.gluster.org/#/c/19552> (yet to be > merged in mainline) in all the active release branches to > avoid users to get > into upgrade failures. The bug and the commit has the > further details. > > > > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://lists.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
