On Thu, Mar 7, 2019 at 10:20 AM Atin Mukherjee <amukh...@redhat.com> wrote:
> I am not sure how BZ 1683815 > <https://bugzilla.redhat.com/show_bug.cgi?id=1683815> can be a blocker at > RC. We have a fix ready, but to me it doesn't look like a blocker. Vijay - > any objections? > None from me as it is an existing minor problem across multiple releases now. I guess it got added as a blocker for RC as I used the URL in the testing day announcement email. We can remove it from the blocker list for RC. Thanks, Vijay > Also the bugzilla dependency of all bugs attached to the release-6 is sort > of messed up. I see most of the times a mainline bug along with its clones > are attached to the tracker which is unnecessary. This has happened because > of default clone but I request every bugzilla assignees to spend few > additional seconds to establish the right dependency. > > I have tried to correct few of them and will do the rest by next Monday. > That’d help us to filter out the unnecessary ones and get to know how many > actual blockers we have. > > On Tue, Mar 5, 2019 at 11:51 PM Shyam Ranganathan <srang...@redhat.com> > wrote: > >> On 3/4/19 12:33 PM, Shyam Ranganathan wrote: >> > On 3/4/19 10:08 AM, Atin Mukherjee wrote: >> >> >> >> >> >> On Mon, 4 Mar 2019 at 20:33, Amar Tumballi Suryanarayan >> >> <atumb...@redhat.com <mailto:atumb...@redhat.com>> wrote: >> >> >> >> Thanks to those who participated. >> >> >> >> Update at present: >> >> >> >> We found 3 blocker bugs in upgrade scenarios, and hence have marked >> >> release >> >> as pending upon them. We will keep these lists updated about >> progress. >> >> >> >> >> >> 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. >> > >> > Based on fixes expected by tomorrow for the upgrade fixes, we will build >> > an RC1 candidate on Wednesday (6-Mar) (tagging early Wed. Eastern TZ). >> > This RC can be used for further testing. >> >> There have been no backports for the upgrade failures, request folks >> working on the same to post a list of bugs that need to be fixed, to >> enable tracking the same. (also, ensure they are marked against the >> release-6 tracker [1]) >> >> Also, we need to start writing out the upgrade guide for release-6, any >> volunteers for the same? >> >> Thanks, >> Shyam >> >> [1] Release-6 tracker bug: >> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.0 >> > -- > - Atin (atinm) >
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel