<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">&lt;<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/20/2018 01:10 PM, Jiffin Thottan wrote:<br>
&gt; Hi Shyam,<br>
&gt;<br>
&gt; Actually I planned to do the release on March 8th(posted the release note on that day). But it didn&#39;t happen.<br>
&gt; I didn&#39;t merge any patches post sending the release note(blocker bug had some merge conflict issue on that so I skipped AFAIR).<br>
&gt; I performed 3.12.7 tagging yesterday and ran the build job today.<br>
&gt;<br>
&gt; 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&#39;s get this moving and get the fix into the next minor release.<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Even though it&#39;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&#39;re running a multi node cluster with brick multiplexing enabled and one node down and there&#39;re some volume operations performed and post that when the node comes back, brick processes fail to come up.<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
&gt;<br>
&gt; --<br>
&gt; Regards,<br>
&gt; Jiffin<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ----- Original Message -----<br>
&gt; From: &quot;Shyam Ranganathan&quot; &lt;<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>&gt;<br>
&gt; To: <a href="mailto:jenkins@build.gluster.org">jenkins@build.gluster.org</a>, <a href="mailto:packaging@gluster.org">packaging@gluster.org</a>, <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
&gt; Sent: Tuesday, March 20, 2018 9:06:57 PM<br>
&gt; Subject: Re: [Gluster-Maintainers] glusterfs-3.12.7 released<br>
&gt;<br>
&gt; On 03/20/2018 11:19 AM, <a href="mailto:jenkins@build.gluster.org">jenkins@build.gluster.org</a> wrote:<br>
&gt;&gt; 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/<wbr>glusterfs-3.12.7.tar.gz</a><br>
&gt;&gt; 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/<wbr>glusterfs-3.12.7.sha512sum</a><br>
&gt;&gt;<br>
&gt;&gt; This release is made off jenkins-release-47<br>
&gt;<br>
&gt; Jiffin, there are about 6 patches ready in the 3.12 queue, that are not<br>
&gt; merged for this release, why?<br>
&gt; <a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>projects/glusterfs,dashboards/<wbr>dashboard:3-12-dashboard</a><br>
&gt;<br>
&gt; The tracker bug for 3.12.7 calls out<br>
&gt; <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1543708" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1543708</a> as a blocker, and<br>
&gt; has a patch, which is not merged.<br>
&gt;<br>
&gt; Was this some test packaging job?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; maintainers mailing list<br>
&gt;&gt; <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
&gt;&gt; <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
&gt;&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; maintainers mailing list<br>
&gt; <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
&gt; <a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
&gt;<br>
</div></div></blockquote></div><br></div></div>