On 10/04/2018 12:01 PM, Atin Mukherjee wrote: > 4) This bug [2] was filed when we released 4.0. > > The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options > missing and hence post-upgrade clients failing the mount). This is > possibly the last chance to fix it. > > Glusterd and protocol maintainers, can you chime in, if this bug needs > to be and can be fixed? (thanks to @anoopcs for pointing it out to me) > > > This is a bad bug to live with. OTOH, I do not have an immediate > solution in my mind on how to make sure (a) these options when > reintroduced are made no-ops, especially they will be disallowed to tune > (with out dirty option check hacks at volume set staging code) . If > we're to tag RC1 tomorrow, I wouldn't be able to take a risk to commit > this change. > > Can we actually have a note in our upgrade guide to document that if > you're upgrading to 4.1 or higher version make sure to disable these > options before the upgrade to mitigate this? Yes, adding this to the "Major Issues" section in the release notes as well as noting it in the upgrade guide is possible. I will go with this option for now, as we do not have complaints around this from 4.0/4.1 releases (which have the same issue as well). _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
