<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Apr 2019 at 10:28, Hari Gowtham <<a href="mailto:hgowtham@redhat.com">hgowtham@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Comments inline.<br>
<br>
On Mon, Apr 1, 2019 at 5:55 AM Sankarshan Mukhopadhyay<br>
<<a href="mailto:sankarshan.mukhopadhyay@gmail.com" target="_blank">sankarshan.mukhopadhyay@gmail.com</a>> wrote:<br>
><br>
> Quite a considerable amount of detail here. Thank you!<br>
><br>
> On Fri, Mar 29, 2019 at 11:42 AM Hari Gowtham <<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a>> wrote:<br>
> ><br>
> > Hello Gluster users,<br>
> ><br>
> > As you all aware that glusterfs-6 is out, we would like to inform you<br>
> > that, we have spent a significant amount of time in testing<br>
> > glusterfs-6 in upgrade scenarios. We have done upgrade testing to<br>
> > glusterfs-6 from various releases like 3.12, 4.1 and 5.3.<br>
> ><br>
> > As glusterfs-6 has got in a lot of changes, we wanted to test those portions.<br>
> > There were xlators (and respective options to enable/disable them)<br>
> > added and deprecated in glusterfs-6 from various versions [1].<br>
> ><br>
> > We had to check the following upgrade scenarios for all such options<br>
> > Identified in [1]:<br>
> > 1) option never enabled and upgraded<br>
> > 2) option enabled and then upgraded<br>
> > 3) option enabled and then disabled and then upgraded<br>
> ><br>
> > We weren't manually able to check all the combinations for all the options.<br>
> > So the options involving enabling and disabling xlators were prioritized.<br>
> > The below are the result of the ones tested.<br>
> ><br>
> > Never enabled and upgraded:<br>
> > checked from 3.12, 4.1, 5.3 to 6 the upgrade works.<br>
> ><br>
> > Enabled and upgraded:<br>
> > Tested for tier which is deprecated, It is not a recommended upgrade.<br>
> > As expected the volume won't be consumable and will have a few more<br>
> > issues as well.<br>
> > Tested with 3.12, 4.1 and 5.3 to 6 upgrade.<br>
> ><br>
> > Enabled, disabled before upgrade.<br>
> > Tested for tier with 3.12 and the upgrade went fine.<br>
> ><br>
> > There is one common issue to note in every upgrade. The node being<br>
> > upgraded is going into disconnected state. You have to flush the iptables<br>
> > and the restart glusterd on all nodes to fix this.<br>
> ><br>
><br>
> Is this something that is written in the upgrade notes? I do not seem<br>
> to recall, if not, I'll send a PR<br>
<br>
No this wasn't mentioned in the release notes. PRs are welcome.<br>
<br>
><br>
> > The testing for enabling new options is still pending. The new options<br>
> > won't cause as much issues as the deprecated ones so this was put at<br>
> > the end of the priority list. It would be nice to get contributions<br>
> > for this.<br>
> ><br>
><br>
> Did the range of tests lead to any new issues?<br>
<br>
Yes. In the first round of testing we found an issue and had to postpone the<br>
release of 6 until the fix was made available.<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1684029" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1684029</a><br>
<br>
And then we tested it again after this patch was made available.<br>
and came across this:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1694010" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1694010</a></blockquote><div dir="auto"><br></div><div dir="auto">This isn’t a bug as we found that upgrade worked seamelessly in two different setup. So we have no issues in the upgrade path to glusterfs-6 release.</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1694010" rel="noreferrer" target="_blank"></a><br>
<br>
Have mentioned this in the second mail as to how to over this situation<br>
for now until the fix is available.<br>
<br>
><br>
> > For the disable testing, tier was used as it covers most of the xlator<br>
> > that was removed. And all of these tests were done on a replica 3 volume.<br>
> ><br>
><br>
> I'm not sure if the Glusto team is reading this, but it would be<br>
> pertinent to understand if the approach you have taken can be<br>
> converted into a form of automated testing pre-release.<br>
<br>
I don't have an answer for this, have CCed Vijay.<br>
He might have an idea.<br>
<br>
><br>
> > Note: This is only for upgrade testing of the newly added and removed<br>
> > xlators. Does not involve the normal tests for the xlator.<br>
> ><br>
> > If you have any questions, please feel free to reach us.<br>
> ><br>
> > [1] <a href="https://docs.google.com/spreadsheets/d/1nh7T5AXaV6kc5KgILOy2pEqjzC3t_R47f1XUXSVFetI/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1nh7T5AXaV6kc5KgILOy2pEqjzC3t_R47f1XUXSVFetI/edit?usp=sharing</a><br>
> ><br>
> > Regards,<br>
> > Hari and Sanju.<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
<br>
<br>
-- <br>
Regards,<br>
Hari Gowtham.<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--Atin</div>