<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 25, 2019 at 9:30 PM Nithya Balachandran <<a href="mailto:nbalacha@redhat.com">nbalacha@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 dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 25 Feb 2019 at 21:12, 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">Time to reset and understand where we are at here. The dates are<br>
slipping, but the tracker is still having the following blockers.<br>
<br>
We need to either understand when these would be fixed, and take a call<br>
on creating 5.4 with known issues not addressed in the blocker, or wait<br>
for the fixes. Responses to the bugs and updates to bugzilla would help<br>
deciding on the same.<br>
<br>
1) Title: glustereventsd does not start on Ubuntu 16.04 LTS<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1649054" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1649054</a><br>
<br>
@aravinda, any updates? Should we wait, of will this take more time?<br>
<br></blockquote><div>IMO, this is not a prio for the interim release as the main focus is the log floods and crashes which are affecting production for a lot of users.</div><div>Can this go into the next release?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2) Title: glusterfs FUSE client crashing every few days with 'Failed to<br>
dispatch handler'<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1671556" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1671556</a><br>
<br>
All patches against the bug are merged, but bug remains in POST state,<br>
as none of the patches claim that the issue "Fixes" the reported problem.<br>
<br>
Are we awaiting more patches for the same? Du/Milind/Nithya?<br></blockquote><div><br></div><div>The crash fixes - this should do for the moment though one user has reported a crash even after turning off wb. IMO, we should go ahead with what we have. <a class="gmail_plusreply" id="gmail-m_-1093892681923116889plusReplyChip-0" href="mailto:rgowdapp@redhat.com" target="_blank">@Raghavendra Gowdappa</a> , what do you think?</div></div></div></blockquote><div><br></div><div>Yes. Actually <a href="https://review.gluster.org/#/c/glusterfs/+/22231/">https://review.gluster.org/#/c/glusterfs/+/22231/</a> says "Fixes", but I think its made dependent on another patch which says "updates". The dependency order should've been other way. This might be the reason why bug state is not changed.</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 dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
3) Title: flooding of "dict is NULL" logging & crash of client process<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1671603" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1671603</a><br>
<br>
Still in NEW state, Du/Amar, do we have a date for resolution?<br>
<br>
Thanks,<br>
Shyam<br>
On 2/18/19 10:13 AM, Shyam Ranganathan wrote:<br>
> We have more blockers against 5.4 now marked. Would like to ask the list<br>
> and understand what we want to get done with by 5.4 and what the<br>
> timeline looks like.<br>
> <br>
> The bug list:<br>
> <a href="https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103&bug_id_type=anddependson&format=tvp</a><br>
> <br>
> 1) <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1649054" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1649054</a><br>
> Title: glustereventsd does not start on Ubuntu 16.04 LTS<br>
> Assignee: Aravinda<br>
> @aravinda can we understand target dates here?<br>
> <br>
> 2) <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1671556" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1671556</a><br>
> Title: glusterfs FUSE client crashing every few days with 'Failed to<br>
> dispatch handler'<br>
> Assignee: Nithya (working on Du and Milind)<br>
> @du/@milind can we get an update on this bug and how far away we are?<br>
> <br>
> 3) <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1671603" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1671603</a><br>
> Title: flooding of "dict is NULL" logging & crash of client process<br>
> Assignee: None (Amar has most of the comments)<br>
> @amar, do we need 2 bugs here? Also, how far away is a fix?<br>
> <br>
> 4) <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1676356" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1676356</a><br>
> Title: glusterfs FUSE client crashing every few days with 'Failed to<br>
> dispatch handler'<br>
> Assignee: Du<br>
> @du, we are still waiting to get<br>
> <a href="https://review.gluster.org/c/glusterfs/+/22189" rel="noreferrer" target="_blank">https://review.gluster.org/c/glusterfs/+/22189</a> merged, right?<br>
> <br>
> Shyam<br>
> On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:<br>
>><br>
>><br>
>> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a><br>
>> <mailto:<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a>>> wrote:<br>
>><br>
>> Adding Raghavendra G and Milind who are working on the patches so<br>
>> they can update on when they should be ready.<br>
>><br>
>> On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a><br>
>> <mailto:<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> There have been several crashes and issues reported by users on the<br>
>> latest 5.3 release. Around 10 patches have been merged since 5.3<br>
>> and we<br>
>> have a few more addressing the blockers against 5.4 [1].<br>
>><br>
>> The original date was March 10th, but we would like to<br>
>> accelerate a 5.4<br>
>> release to earlier this month, once all critical blockers are fixed.<br>
>><br>
>> Hence there are 3 asks in this mail,<br>
>><br>
>> 1) Packaging team, would it be possible to accommodate an 5.4<br>
>> release<br>
>> around mid-next week (RC0 for rel-6 is also on the same week)?<br>
>> Assuming<br>
>> we get the required fixes by then.<br>
>><br>
>> 2) Maintainers, what other issues need to be tracked as<br>
>> blockers? Please<br>
>> add them to [1].<br>
>><br>
>> 3) Current blocker status reads as follows:<br>
>> - Bug 1651246 - Failed to dispatch handler<br>
>> - This shows 2 patches that are merged, but there is no patch that<br>
>> claims this is "Fixed" hence bug is still in POST state. What other<br>
>> fixes are we expecting on this?<br>
>> - @Milind request you to update the status<br>
>><br>
>> - Bug 1671556 - glusterfs FUSE client crashing every few days with<br>
>> 'Failed to dispatch handler'<br>
>> - Awaiting fixes for identified issues<br>
>> - @Nithya what would be the target date?<br>
>><br>
>><br>
>> Fix @ <a href="https://review.gluster.org/#/c/glusterfs/+/22189/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c/glusterfs/+/22189/</a><br>
>><br>
>> waiting on reviews. I am hoping to get this merged by end of this week<br>
>> and send a backport.<br>
>><br>
>><br>
>> - Bug 1671603 - flooding of "dict is NULL" logging & crash of<br>
>> client process<br>
>> - Awaiting a fix, what is the potential target date for the same?<br>
>> - We also need the bug assigned to a person<br>
>><br>
>> Thanks,<br>
>> Shyam<br>
>><br>
>> [1] Release 5.4 tracker:<br>
>> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4</a><br>
>> _______________________________________________<br>
>> maintainers mailing list<br>
>> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a> <mailto:<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a>><br>
>> <a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
>><br>
> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
> <br>
</blockquote></div></div>
</blockquote></div></div></div>