<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 22, 2018 at 12:38 PM, Jiffin Tony Thottan <span dir="ltr"><<a href="mailto:jthottan@redhat.com" target="_blank">jthottan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<p><br>
</p>
<br>
<div class="m_-6495844601584204850moz-cite-prefix">On Thursday 22 March 2018 12:29 PM,
Jiffin Tony Thottan wrote:<br>
</div>
<blockquote type="cite">
<p><br>
</p>
<br>
<div class="m_-6495844601584204850moz-cite-prefix">On Wednesday 21 March 2018 09:06 AM,
Atin Mukherjee wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Mar 21, 2018 at 12:18 AM,
Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 03/20/2018 01:10 PM, Jiffin Thottan wrote:<br>
> Hi Shyam,<br>
><br>
> Actually I planned to do the release on March
8th(posted the release note on that day). But it
didn't happen.<br>
> I didn't merge any patches post sending the
release note(blocker bug had some merge conflict issue
on that so I skipped AFAIR).<br>
> I performed 3.12.7 tagging yesterday and ran the
build job today.<br>
><br>
> Can u please provide a suggestion here ? Do I
need to perform a 3.12.7-1 for the blocker bug ?<br>
<br>
</span>I see that the bug is marked against the tracker,
but is not a<br>
regression or an issue that is serious enough that it
cannot wait for<br>
the next minor release.<br>
<br>
Copied Atin to the mail, who opened that issue for his
comments. If he<br>
agrees, let's get this moving and get the fix into the
next minor release.
<div class="m_-6495844601584204850HOEnZb">
<div class="m_-6495844601584204850h5"><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Even though it's not a regression and a day 1 bug
with brick multiplexing, the issue is severe enough to
consider this to be fixed *asap* . In this scenario, if
you're running a multi node cluster with brick
multiplexing enabled and one node down and there're some
volume operations performed and post that when the node
comes back, brick processes fail to come up.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Issue is impact only with glusterd, whether any other component
needs this fix?<br>
</blockquote>
<br></span>
Sorry I meant brick multiplexing not glusterd<br>
--<br>
Jiffin<div><div class="h5"><br>
<blockquote type="cite"> If it
is issue not report from upstream user/community, I prefer to take
it for next release.<br></blockquote></div></div></div></blockquote><div><br></div><div>IMO, assessment of an issue should be done based on its merit, not based on where it originates from. It might be a fair question to ask that "do we have users who have brick multiplexing enabled" and based on that take a call to fix it immediately or as part of next update but at the same time, you're still exposing a known problem with out flagging a warning that don't use brick multiplexing till this bug is fixed.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><div class="h5"><blockquote type="cite">
<br>
Regards,<br>
Jiffin<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_-6495844601584204850HOEnZb">
<div class="m_-6495844601584204850h5"> ><br>
> --<br>
> Regards,<br>
> Jiffin<br>
><br>
><br>
><br>
><br>
> ----- Original Message -----<br>
> From: "Shyam Ranganathan" <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>><br>
> To: <a href="mailto:jenkins@build.gluster.org" target="_blank">jenkins@build.gluster.org</a>,
<a href="mailto:packaging@gluster.org" target="_blank">packaging@gluster.org</a>,
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
> Sent: Tuesday, March 20, 2018 9:06:57 PM<br>
> Subject: Re: [Gluster-Maintainers]
glusterfs-3.12.7 released<br>
><br>
> On 03/20/2018 11:19 AM, <a href="mailto:jenkins@build.gluster.org" target="_blank">jenkins@build.gluster.org</a>
wrote:<br>
>> SRC: <a href="https://build.gluster.org/job/release-new/47/artifact/glusterfs-3.12.7.tar.gz" rel="noreferrer" target="_blank">https://build.gluster.org/job/<wbr>release-new/47/artifact/gluste<wbr>rfs-3.12.7.tar.gz</a><br>
>> HASH: <a href="https://build.gluster.org/job/release-new/47/artifact/glusterfs-3.12.7.sha512sum" rel="noreferrer" target="_blank">https://build.gluster.org/job/<wbr>release-new/47/artifact/gluste<wbr>rfs-3.12.7.sha512sum</a><br>
>><br>
>> This release is made off jenkins-release-47<br>
><br>
> Jiffin, there are about 6 patches ready in the
3.12 queue, that are not<br>
> merged for this release, why?<br>
> <a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard" rel="noreferrer" target="_blank">https://review.gluster.org/#/p<wbr>rojects/glusterfs,dashboards/d<wbr>ashboard:3-12-dashboard</a><br>
><br>
> The tracker bug for 3.12.7 calls out<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1543708" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1543708</a>
as a blocker, and<br>
> has a patch, which is not merged.<br>
><br>
> Was this some test packaging job?<br>
><br>
><br>
><br>
><br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> maintainers mailing list<br>
>> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
>> <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/maintainers</a><br>
>><br>
> ______________________________<wbr>_________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/maintainers</a><br>
><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<br>
<fieldset class="m_-6495844601584204850mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
maintainers mailing list
<a class="m_-6495844601584204850moz-txt-link-abbreviated" href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a>
<a class="m_-6495844601584204850moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/maintainers" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br></div></div>