Got it! Thanks On Monday, 2 November 2015, Atin Mukherjee <[email protected]> wrote:
> Here is an update to this issue. Gaurav Garg (In Cc) has identified the > root cause and the fix [1] has been posted for review in mainline. Once > its merged we will backport it and push it for 3.7.6. > > The issue originated because of introducing new enums in the middle of > the enum structure which resulted in a mismatch in enum number at the > receiving glusterd end and caused commands to fail. Fix is to move these > new enums at the end of the structure, however this would not fix 3.7.5 > to 3.7.6 upgrade path as the same mismatch will happen in this case too. > However if you upgrade the complete cluster, then the issue goes off. We > could have chosen to maintain two different enum structures here (one > for pre 3.7.6 and the other is >= 3.7.6) but that makes code look > redundant and more importantly ugly. So we chose to go with option 1. > Another BZ will be raised to mark 3.7.5 to 3.7.6 upgrade issue as known > issue and the same will be captured in the release notes. > > 3.7.7 onward the upgrade path will be smooth. > > [1] http://review.gluster.org/#/c/12473/ > > Thanks, > Atin > > > On 10/28/2015 06:23 PM, Raghavendra Talur wrote: > > I have filed a bug for this on bugzilla. > > Here is the link https://bugzilla.redhat.com/show_bug.cgi?id=1276029. > > > > Please cc yourself for updates on the bug. > > > > > > Thanks, > > Raghavendra Talur > > > > > > _______________________________________________ > > Gluster-devel mailing list > > [email protected] <javascript:;> > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > -- ..................................................................... Juan Francisco Rodríguez Cardoso [email protected] | +34 636 692 691 www.keedio.com .....................................................................
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
