<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 4 Mar 2019 at 20:33, Amar Tumballi Suryanarayan <<a href="mailto:atumball@redhat.com">atumball@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks to those who participated.<br>
<br>
Update at present:<br>
<br>
We found 3 blocker bugs in upgrade scenarios, and hence have marked release<br>
as pending upon them. We will keep these lists updated about progress.</blockquote><div dir="auto"><br></div><div dir="auto">I’d like to clarify that upgrade testing is blocked. So just fixing these test blocker(s) isn’t enough to call release-6 green. We need to continue and finish the rest of the upgrade tests once the respective bugs are fixed.</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
-Amar<br>
<br>
On Mon, Feb 25, 2019 at 11:41 PM Amar Tumballi Suryanarayan <<br>
<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
> We are calling out our users, and developers to contribute in validating<br>
> ‘glusterfs-6.0rc’ build in their usecase. Specially for the cases of<br>
> upgrade, stability, and performance.<br>
><br>
> Some of the key highlights of the release are listed in release-notes<br>
> draft<br>
> <<a href="https://github.com/gluster/glusterfs/blob/release-6/doc/release-notes/6.0.md" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs/blob/release-6/doc/release-notes/6.0.md</a>>.<br>
> Please note that there are some of the features which are being dropped out<br>
> of this release, and hence making sure your setup is not going to have an<br>
> issue is critical. Also the default lru-limit option in fuse mount for<br>
> Inodes should help to control the memory usage of client processes. All the<br>
> good reason to give it a shot in your test setup.<br>
><br>
> If you are developer using gfapi interface to integrate with other<br>
> projects, you also have some signature changes, so please make sure your<br>
> project would work with latest release. Or even if you are using a project<br>
> which depends on gfapi, report the error with new RPMs (if any). We will<br>
> help fix it.<br>
><br>
> As part of test days, we want to focus on testing the latest upcoming<br>
> release i.e. GlusterFS-6, and one or the other gluster volunteers would be<br>
> there on #gluster channel on freenode to assist the people. Some of the key<br>
> things we are looking as bug reports are:<br>
><br>
> -<br>
><br>
> See if upgrade from your current version to 6.0rc is smooth, and works<br>
> as documented.<br>
> - Report bugs in process, or in documentation if you find mismatch.<br>
> -<br>
><br>
> Functionality is all as expected for your usecase.<br>
> - No issues with actual application you would run on production etc.<br>
> -<br>
><br>
> Performance has not degraded in your usecase.<br>
> - While we have added some performance options to the code, not all of<br>
> them are turned on, as they have to be done based on usecases.<br>
> - Make sure the default setup is at least same as your current<br>
> version<br>
> - Try out few options mentioned in release notes (especially,<br>
> --auto-invalidation=no) and see if it helps performance.<br>
> -<br>
><br>
> While doing all the above, check below:<br>
> - see if the log files are making sense, and not flooding with some<br>
> “for developer only” type of messages.<br>
> - get ‘profile info’ output from old and now, and see if there is<br>
> anything which is out of normal expectation. Check with us on the numbers.<br>
> - get a ‘statedump’ when there are some issues. Try to make sense<br>
> of it, and raise a bug if you don’t understand it completely.<br>
><br>
><br>
> <<a href="https://hackmd.io/YB60uRCMQRC90xhNt4r6gA?both#Process-expected-on-test-days" rel="noreferrer" target="_blank">https://hackmd.io/YB60uRCMQRC90xhNt4r6gA?both#Process-expected-on-test-days</a>>Process<br>
> expected on test days.<br>
><br>
> -<br>
><br>
> We have a tracker bug<br>
> <<a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.0" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.0</a>>[0]<br>
> - We will attach all the ‘blocker’ bugs to this bug.<br>
> -<br>
><br>
> Use this link to report bugs, so that we have more metadata around<br>
> given bugzilla.<br>
> - Click Here<br>
> <<a href="https://bugzilla.redhat.com/enter_bug.cgi?blocked=1672818&bug_severity=high&component=core&priority=high&product=GlusterFS&status_whiteboard=gluster-test-day&version=6" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/enter_bug.cgi?blocked=1672818&bug_severity=high&component=core&priority=high&product=GlusterFS&status_whiteboard=gluster-test-day&version=6</a>><br>
> [1]<br>
> -<br>
><br>
> The test cases which are to be tested are listed here in this sheet<br>
> <<a href="https://docs.google.com/spreadsheets/d/1AS-tDiJmAr9skK535MbLJGe_RfqDQ3j1abX1wtjwpL4/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1AS-tDiJmAr9skK535MbLJGe_RfqDQ3j1abX1wtjwpL4/edit?usp=sharing</a>>[2],<br>
> please add, update, and keep it up-to-date to reduce duplicate efforts</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">- Atin (atinm)</div>