<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 4, 2018 at 9:03 PM Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 09/13/2018 11:10 AM, Shyam Ranganathan wrote:<br>
> RC1 would be around 24th of Sep. with final release tagging around 1st<br>
> of Oct.<br>
<br>
RC1 now stands to be tagged tomorrow, and patches that are being<br>
targeted for a back port include,<br>
<br>
1) <a href="https://review.gluster.org/c/glusterfs/+/21314" rel="noreferrer" target="_blank">https://review.gluster.org/c/glusterfs/+/21314</a> (snapshot volfile in<br>
mux cases)<br>
<br>
@RaBhat working on this.<br>
<br>
2) Py3 corrections in master<br>
<br>
@Kotresh are all changes made to master backported to release-5 (may not<br>
be merged, but looking at if they are backported and ready for merge)?<br>
<br>
3) Release notes review and updates with GD2 content pending<br>
<br>
@Kaushal/GD2 team can we get the updates as required?<br>
<a href="https://review.gluster.org/c/glusterfs/+/21303" rel="noreferrer" target="_blank">https://review.gluster.org/c/glusterfs/+/21303</a><br>
<br>
4) This bug [2] was filed when we released 4.0.<br>
<br>
The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options<br>
missing and hence post-upgrade clients failing the mount). This is<br>
possibly the last chance to fix it.<br>
<br>
Glusterd and protocol maintainers, can you chime in, if this bug needs<br>
to be and can be fixed? (thanks to @anoopcs for pointing it out to me)<br></blockquote><div><br></div><div>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.</div><div><br></div><div>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?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The tracker bug [1] does not have any other blockers against it, hence<br>
assuming we are not tracking/waiting on anything other than the set above.<br>
<br>
Thanks,<br>
Shyam<br>
<br>
[1] Tracker: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0</a><br>
[2] Potential upgrade bug:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1540659" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1540659</a><br>
</blockquote></div></div>