[Gluster-infra] [Bug 1355931] not able to git pull the source

2016-07-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1355931

Nigel Babu  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||nig...@redhat.com
   Assignee|b...@gluster.org|nig...@redhat.com



--- Comment #1 from Nigel Babu  ---
Restarted gerrit to fix the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=UP0JcdN5MR=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1355931] New: not able to git pull the source

2016-07-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1355931

Bug ID: 1355931
   Summary: not able to git pull the source
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: amukh...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



Description of problem:

Along with git pull, even review.gluster.org is not responding.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=mgN2fXu1FL=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1355808] slave29.cloud.gluster.org does not have an xfs partition at /d

2016-07-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1355808



--- Comment #1 from Nigel Babu  ---
I've disabled the machine from Jenkins so it doesn't get assigned jobs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=CTji2XtYuB=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1354422] Regression tests do not set the right paths

2016-07-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1354422



--- Comment #4 from Nigel Babu  ---
I've set it on the job itself, rather than the machine. So it should work
across all machines.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=Wzl2xAw0ZX=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] tests/basic/op_errnos.t failure

2016-07-12 Thread Nigel Babu 
Please file a bug against project-infrastructure.

On Tue, Jul 12, 2016 at 6:50 PM, Raghavendra Talur 
wrote:

> Nigel/Misc,
>
> Could you please look into this?
> slave29 does not seem to have a xfs formatted backend for tests.
>
> Thanks,
> Raghavendra Talur
>
> On Tue, Jul 12, 2016 at 6:41 PM, Avra Sengupta 
> wrote:
>
>> Atin,
>>
>> I am not sure about the docker containers, but both the failures you
>> mentioned are in slave29, which as Talur explained is missing the
>> appropriate backend filesystem. Owing to this, op-errno.t is just the tip
>> of the iceberg, and every other test that uses lvm will fail in this
>> particular slave will fail too.
>>
>> Talur,
>> Thanks for looking into it. It is indeed strange this. I checked the
>> dmesg and the /var/log/messages in this slave and I couldn't find any
>> relevant log.
>>
>>
>> On 07/12/2016 05:29 PM, Raghavendra Talur wrote:
>>
>> I checked the machine.
>>
>> Here is the df -hT output
>> [jenkins@slave29 ~]$ cat /etc/fstab
>> # Accessible filesystems, by reference, are maintained under '/dev/disk'
>> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more
>> info
>> #
>> /dev/xvda1  /   ext3
>>  defaults,noatime,barrier=0 1 1
>> tmpfs   /dev/shmtmpfs   defaults0
>> 0
>> devpts  /dev/ptsdevpts  gid=5,mode=620  0
>> 0
>> sysfs   /syssysfs   defaults0
>> 0
>> proc/proc   procdefaults0
>> 0
>> #/dev/xvdc1 noneswapsw  0
>> 0
>>
>>
>> We don't see a xfs device mounted at /d and / is of type ext3 which does
>> not support fallocate. The uptime of the machine is 73 days though. I don't
>> know how the /d xfs partition vanished.
>>
>> On Tue, Jul 12, 2016 at 4:54 PM, Atin Mukherjee < 
>> amukh...@redhat.com> wrote:
>>
>>>
>>> https://build.gluster.org/job/rackspace-regression-2GB-triggered/22156/consoleFull
>>> - another failure
>>>
>>> On Tue, Jul 12, 2016 at 4:42 PM, Atin Mukherjee < 
>>> amukh...@redhat.com> wrote:
>>>


 On Tue, Jul 12, 2016 at 4:36 PM, Avra Sengupta < 
 aseng...@redhat.com> wrote:

> Hi Atin,
>
> Please check the testcase result in the console. It clearly states the
> reason of the failure. A quick search of 30815, as shown in the testcase
> shows that the error that is generated is a thinp issue, and we can see
> fallocate failing and lvm not properly being setup in the environment.
>

 While this is valid for my docker containers, I am just wondering why
 did this happen in jenkins slave?


> Regards,
> Avra
>
> P.S Here are the logs from the console stating so.
>
> *02:50:34* [09:50:34] Running tests in file 
> ./tests/basic/op_errnos.t*02:50:41* fallocate: 
> /d/backends/patchy_snap_vhd: fallocate failed: Operation not 
> supported*02:50:41* losetup: /d/backends/patchy_snap_vhd: warning: file 
> smaller than 512 bytes, the loop device maybe be useless or invisible for 
> system tools.*02:50:41*   Device /d/backends/patchy_snap_loop not found 
> (or ignored by filtering).*02:50:41*   Device 
> /d/backends/patchy_snap_loop not found (or ignored by 
> filtering).*02:50:41*   Unable to add physical volume 
> '/d/backends/patchy_snap_loop' to volume group 
> 'patchy_snap_vg_1'.*02:50:41*   Volume group "patchy_snap_vg_1" not 
> found*02:50:41*   Cannot process volume group patchy_snap_vg_1*02:50:42*  
>  Volume group "patchy_snap_vg_1" not found*02:50:42*   Cannot process 
> volume group patchy_snap_vg_1*02:50:42* /dev/patchy_snap_vg_1/brick_lvm: 
> No such file or directory*02:50:42* Usage: mkfs.xfs*02:50:42* /* 
> blocksize */ [-b log=n|size=num]*02:50:42* /* data subvol */ 
> [-d agcount=n,agsize=n,file,name=xxx,size=num,*02:50:42*  
>   (sunit=value,swidth=value|su=num,sw=num),*02:50:42* 
> sectlog=n|sectsize=num*02:50:42* /* inode size */   [-i 
> log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,*02:50:42*  
>   projid32bit=0|1]*02:50:42* /* log subvol */ [-l 
> agnum=n,internal,size=num,logdev=xxx,version=n*02:50:42*  
>   sunit=value|su=num,sectlog=n|sectsize=num,*02:50:42*
> lazy-count=0|1]*02:50:42* /* label */   [-L label 
> (maximum 12 characters)]*02:50:42* /* naming */   [-n 
> log=n|size=num,version=2|ci]*02:50:42* /* prototype file */ [-p 
> fname]*02:50:42* /* quiet */[-q]*02:50:42* /* realtime 
> subvol */[-r extsize=num,size=num,rtdev=xxx]*02:50:42* /* sectorsize 
> */  [-s

[Gluster-infra] [Bug 1354422] Regression tests do not set the right paths

2016-07-12 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1354422

Poornima G  changed:

   What|Removed |Added

  Flags|needinfo?(pgurusid@redhat.c |
   |om) |



--- Comment #2 from Poornima G  ---
Nigel,

If the chroot of source install is /build/install, then:
export PKG_CONFIG_PATH="/build/install/lib/pkgconfig" needs to be set on all
the slaves.

LIBRARY_PATH, C_INCLUDE_PATH are not required as PKG_CONFIG_PATH will have the
path for lib and header

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=0TN5dbAlGM=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra