<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 30 June 2016 at 14:09, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@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 class="HOEnZb"><div class="h5">On Thu, Jun 30, 2016 at 10:27:23AM +0200, Niels de Vos wrote:<br>
> On Thu, Jun 30, 2016 at 12:46:57PM +0530, Atin Mukherjee wrote:<br>
> > On Thu, Jun 30, 2016 at 11:56 AM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>><br>
> > wrote:<br>
> ><br>
> > ><br>
> > ><br>
> > > On Thu, Jun 30, 2016 at 11:08 AM, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
> > ><br>
> > >> Hi all,<br>
> > >><br>
> > >> I'm (or was) planning to do a 3.7.13 release on schedule today. 3.7.12<br>
> > >> has a huge issue with libgfapi, solved by [1].<br>
> > >> I'm not sure if this fixes the other issues with libgfapi noticed by<br>
> > >> Lindsay on gluster-users.<br>
> > >><br>
> > >> This patch has been included in the packages 3.7.12 built for CentOS,<br>
> > >> Fedora, Ubuntu, Debian and SUSE. I guess Lindsay is using one of these<br>
> > >> packages, so it might be that the issue seen is new. So I'd like to do<br>
> > >> a quick release once we have a fix.<br>
> > >><br>
> > ><br>
> > > <a href="http://review.gluster.org/14835" rel="noreferrer" target="_blank">http://review.gluster.org/14835</a> probably is the one you are looking for.<br>
> > ><br>
> > ><br>
> ><br>
> > Ignore it. I had a chance to talk to Poornima and she mentioned that this<br>
> > is a different problem.<br>
><br>
> The patch that fixes the problem is <a href="http://review.gluster.org/14822" rel="noreferrer" target="_blank">http://review.gluster.org/14822</a> and<br>
> I've merged it yesterday. The problem was introduced by<br>
> <a href="http://review.gluster.org/14822" rel="noreferrer" target="_blank">http://review.gluster.org/14822</a> (similar subject as 12835 above).<br>
> Unfortunately none of the libgfapi maintainer did completely review the<br>
> change before it got merged. It also seems that minimal testing was done<br>
> after the change got included (last minute change in 3.8, quickly<br>
> backported as well).<br>
><br>
> In order to make Gluster more stable, and prevent problems like this<br>
> again, we really need to work on automating test cases. I hope all<br>
> maintainers are thinking about how they want to test the components they<br>
> are responsible for. For example, I'm planning to run the upstream QEMU<br>
> tests against our nightly builds (libgfapi), and similar for the<br>
> connectathon tests (Gluster/NFS). At one point it should be possible to<br>
> wrap these in DiSTAF, but the DiSTAF job in the CentOS CI is not ready<br>
> yet.<br>
><br>
> Thanks,<br>
> Niels<br>
><br>
><br>
> ><br>
> ><br>
> > ><br>
> > >> Maintainers can merge changes into release-3.7 that follow the<br>
> > >> criteria given in [2]. Please make sure to add the bugs for patches<br>
> > >> you are merging are added as dependencies for the 3.7.13 tracker bug<br>
> > >> [3].<br>
> > >><br>
> > >> Thanks,<br>
> > >> Kaushal<br>
> > >><br>
> > >> [1]: <a href="https://review.gluster.org/14822" rel="noreferrer" target="_blank">https://review.gluster.org/14822</a><br>
> > >> [2]: <a href="https://public.pad.fsfe.org/p/glusterfs-release-process-201606" rel="noreferrer" target="_blank">https://public.pad.fsfe.org/p/glusterfs-release-process-201606</a><br>
> > >> under the GlusterFS minor release heading<br>
> > >> [3]: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.7.13" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.7.13</a><br>
> > >> _______________________________________________<br>
> > >> maintainers mailing list<br>
> > >> <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
> > >> <a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
> > >><br>
> > ><br>
> > ><br>
><br>
> > _______________________________________________<br>
> > maintainers mailing list<br>
> > <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
><br>
<br>
<br>
<br>
</div></div>> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
What needs to happen for DiSTAF job on Centos CI? I'm pushing hard to get more<br>
DiSTAF tests upstream. I can help solve the pipeline/infra issues related to<br>
this.<br></blockquote><div><br></div><div>I have replied about this in other mail. Basically we just need integration with gdeploy (or similar tool) to install gluster and create the xfs backend for starting the distaf run.</div><div><br></div><div>The other issue was not having the disks in the machines provisioned by duffy. But this was discussed and IIRC the temporary solution was to run with loopback mount.</div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div><br></div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
--<br>
nigelb<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div></div>