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