On 3 July 2016 at 17:10, Niels de Vos <nde...@redhat.com> wrote: > On Thu, Jun 30, 2016 at 08:09:31PM +0530, M S Vishwanath Bhat wrote: > > On 30 June 2016 at 14:09, Nigel Babu <nig...@redhat.com> 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 < > amukh...@redhat.com> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jun 30, 2016 at 11:08 AM, Kaushal M <kshlms...@gmail.com > > > > > 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 > > > > > >> maintain...@gluster.org > > > > > >> http://www.gluster.org/mailman/listinfo/maintainers > > > > > >> > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > maintainers mailing list > > > > > maintain...@gluster.org > > > > > http://www.gluster.org/mailman/listinfo/maintainers > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Gluster-devel mailing list > > > > Gluster-devel@gluster.org > > > > 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. > > Yes, the physical systems in the CentOS CI do not have spare, > unpartitioned disks. Creating an image file and using that as disk is > the suggested workaround. > > Creating disks is pretty simple, this works just fine (needs some work > for reboot cases): > > [root@vm016 ~]# fallocate -l 1G /var/tmp/brick_01.img > [root@vm016 ~]# losetup -f /var/tmp/brick_01.img > [root@vm016 ~]# losetup -l > NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE > /dev/loop0 0 0 0 0 /var/tmp/brick_01.img > [root@vm016 ~]# pvcreate /dev/loop0 > Physical volume "/dev/loop0" successfully created > [root@vm016 ~]# vgcreate brick_01 /dev/loop0 > Volume group "brick_01" successfully created > [root@vm016 ~]# vgs > VG #PV #LV #SN Attr VSize VFree > brick_01 1 0 0 wz--n- 1020.00m 1020.00m >
Thanks Niels. This is more helpful. I couldn't put as much work as I wanted to but getting something done. I have something written today, but will test that tomorrow (I still need to find my ssh keys to get access to CentOS jumphost. Best Regards, Vishwanath > > > HTH, > Niels > > > > > Best Regards, > > Vishwanath > > > > > > Best Regards, > > Vishwanath > > > > > > > > > > > > > > > -- > > > nigelb > > > _______________________________________________ > > > Gluster-devel mailing list > > > Gluster-devel@gluster.org > > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > >
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel