<div dir="ltr"><div><div><div>Kotresh,<br><br></div>Can you please take care of capturing this in both 3.7.13 & 3.8.1 release notes? Content is already available in the mail thread.<br><br></div>Thanks,<br></div>Atin<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 20, 2016 at 8:10 PM, Niels de Vos <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','ndevos@redhat.com');" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tue, Jul 12, 2016 at 11:26:46AM +0530, Atin Mukherjee wrote:<br>
> I still see the release notes for 3.8.1 & 3.7.13 not reflecting this<br>
> change.<br>
><br>
> Niels, Kaushal,<br>
><br>
> Shouldn't we highlight this as early as possible to the users given release<br>
> note is the best possible medium to capture all the known issues and the<br>
> work around?<br>
<br>
</span>You can sent a patch to the release notes:<br>
<a href="https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.1.md" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.1.md</a><br>
<br>
The release notes of the previous version are normallky used/copied and<br>
modified for the new version. A new section "known issues" before the<br>
"Bugs addressed" would be good.<br>
<br>
Thanks,<br>
Niels<br>
<div><div><br>
<br>
> ~Atin<br>
><br>
><br>
> On Sat, Jul 9, 2016 at 10:02 PM, Atin Mukherjee <<a href="javascript:_e(%7B%7D,'cvml','amukherj@redhat.com');" target="_blank">amukherj@redhat.com</a>> wrote:<br>
><br>
> > We have hit a bug 1347250 in downstream (applicable upstream too) where it<br>
> > was seen that glusterd didnt regenerate the volfiles when it was interimly<br>
> > brought up with upgrade mode by yum. Log file captured that gsyncd<br>
> > --version failed to execute and hence glusterd init couldnt proceed till<br>
> > the volfile regeneration. Since the ret code is not handled here in spec<br>
> > file users wouldnt come to know about this and going forward this is going<br>
> > to cause major issues in healing and all and finally it exploits the<br>
> > possibility of split brains at its best.<br>
> ><br>
> > Further analysis by Kotresh & Raghavendra Talur reveals that gsyncd failed<br>
> > here because of the compatibility issue where gsyncd was still not upgraded<br>
> > where as glusterfs-server was and this failure was mainly because of change<br>
> > in the mem type enum. We have seen a similar issue for RDMA as well<br>
> > (probably a year back). So to be very generic this can happen in any<br>
> > upgrade path from one version to another where new mem type is introduced.<br>
> > We have seen this from 3.7.8 to 3.7.12 and 3.8. People upgrading from 3.6<br>
> > to 3.7/3.8 will also experience this issue.<br>
> ><br>
> > Till we work on this fix, I suggest all the release managers to highlight<br>
> > this in the release note of the latest releases with the following work<br>
> > around after yum update:<br>
> ><br>
> > 1. grep -irns "geo-replication module not working as desired" /var/log/glusterfs/etc-glusterfs-glusterd.vol.log | wc -l<br>
> ><br>
> > If the output is non-zero, then go to step 2 else follow the rest of the steps as per the guide.<br>
> ><br>
> > 2.Check if glusterd instance is running or not by 'ps aux | grep glusterd', if it is, then stop the glusterd service.<br>
> ><br>
> > 3. glusterd --xlator-option *.upgrade=on -N<br>
> ><br>
> > and then proceed ahead with rest of the steps as per the guide.<br>
> ><br>
> > Thoughts?<br>
> ><br>
> > P.S : this email is limited to maintainers till we decide on the approach<br>
> > to highlight this issues to the users<br>
> ><br>
> ><br>
> > --<br>
> > Atin<br>
> > Sent from iPhone<br>
> ><br>
<br>
</div></div><div><div>> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="javascript:_e(%7B%7D,'cvml','maintainers@gluster.org');" target="_blank">maintainers@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</div>
<br><br>-- <br>Atin<br>Sent from iPhone<br>