<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 7, 2019 at 10:20 AM Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><div>I am not sure how BZ <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1683815" target="_blank">1683815</a> can be a blocker at RC. We have a fix ready, but to me it doesn't look like a blocker. Vijay - any objections?</div></div></div></blockquote><div><br></div><div>None from me as it is an existing minor problem across multiple releases now.</div><div><br></div><div>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.</div><div><br></div><div>Thanks,</div><div>Vijay</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><div><br></div><div>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.<br></div><div dir="auto"><br></div><div dir="auto">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.</div></div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 11:51 PM Shyam Ranganathan <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 3/4/19 12:33 PM, Shyam Ranganathan wrote:<br>> On 3/4/19 10:08 AM, Atin Mukherjee wrote:<br>>><br>>><br>>> On Mon, 4 Mar 2019 at 20:33, Amar Tumballi Suryanarayan<br>>> <<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a> <mailto:<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>>> wrote:<br>>><br>>> Thanks to those who participated.<br>>><br>>> Update at present:<br>>><br>>> We found 3 blocker bugs in upgrade scenarios, and hence have marked<br>>> release<br>>> as pending upon them. We will keep these lists updated about progress.<br>>><br>>><br>>> I’d like to clarify that upgrade testing is blocked. So just fixing<br>>> these test blocker(s) isn’t enough to call release-6 green. We need to<br>>> continue and finish the rest of the upgrade tests once the respective<br>>> bugs are fixed.<br>> <br>> Based on fixes expected by tomorrow for the upgrade fixes, we will build<br>> an RC1 candidate on Wednesday (6-Mar) (tagging early Wed. Eastern TZ).<br>> This RC can be used for further testing.<br>
<br>There have been no backports for the upgrade failures, request folks<br>working on the same to post a list of bugs that need to be fixed, to<br>enable tracking the same. (also, ensure they are marked against the<br>release-6 tracker [1])<br>
<br>Also, we need to start writing out the upgrade guide for release-6, any<br>volunteers for the same?<br>
<br>Thanks,<br>Shyam<br>
<br>[1] Release-6 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><br>
</blockquote></div>
</div>-- <br><div dir="ltr" class="gmail-m_7322173390662646872gmail_signature">- Atin (atinm)</div>
</blockquote></div></div>