[Gluster-infra] [Bug 1470285] Beta.Gluster.org IP address

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1470285



--- Comment #10 from Amye Scavarda  ---
So I'm having trouble sorting this, is there somewhere I can look to see what
the comminfra team does support?

-- 
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=QZly1838Rk=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1471029] need access to centos for using the core file

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1471029

Nigel Babu  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
 CC||nig...@redhat.com



--- Comment #1 from Nigel Babu  ---
Machine loaned.

-- 
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=9s8YscjiiT=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1452618] Requesting centos machine to test regression test failures

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1452618

Nigel Babu  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2017-07-14 06:07:15



--- Comment #5 from Nigel Babu  ---
Machine back in the pool.

-- 
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=hIAJ0Pz3HQ=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1471029] New: need access to centos for using the core file

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1471029

Bug ID: 1471029
   Summary: need access to centos for using the core file
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: hgowt...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



Created attachment 1298224
  --> https://bugzilla.redhat.com/attachment.cgi?id=1298224=edit
hari's public key

Description of problem:
need access to this console [1] to take a look at the core file

[1] https://build.gluster.org/job/centos6-regression/5433/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
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=JFVk9TZTPB=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Jenkins and Gerrit issues today

[Nigel Babu]

Note: I've retriggered smoke/regression where appropriate for all patches
posted since the issue started.

On Fri, Jul 14, 2017 at 1:00 PM, Nigel Babu  wrote:

> Hello,
>
> ## Highlights
> * If you pushed a patch today or did "recheck centos", please do a
> recheck. Those jobs were not triggered.
> * Please actually verify that the jobs for your patches have started. You
> can do that by visiting https://build.gluster.org/job/smoke/ (for smoke)
> or https://build.gluster.org/job/centos6-regression/ (for regression) and
> searching for your review. Verify that the patchset is correct.
>
> ## The Details
>
> This morning I installed critical security updates for Jenkins that needed
> a restart of Jenkins. After this restart, it appears that the Gerrit plugin
> failed to load because of an XML error in the config file. As far as I
> know, this error has always existed, but the newer version of the plugin
> became more strict in xml parsing. I noticed this only about an hour so ago
> and I've fixed it. Please let me know if there are further problems. Due to
> this any jobs that should have been triggered since about 8:30 am this
> morning were not triggered. Please manually do a recheck for your patches.
>
> Additionally, Ravi and Nithya pointed me to a problem where Gerrit wasn't
> responding. We've noticed this quite often because we've configured Gerrit
> to not drop idle connections. This forces us to restart Gerrit when there
> are too many long-running idle connections. I've put a timeout of 10 mins
> for idle connections. This issue should be sorted.
>
> However, Jenkins does an SSH connection with Gerrit by running `ssh
> jenk...@review.gluster.org stream-events`. I'm not sure if this Gerrit
> config change will cause a conflict with Jenkins, but we'll see in the next
> few hours. None of the documentation explicitly points to a problem.
>
> --
> nigelb
>



-- 
nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] Jenkins and Gerrit issues today

[Nigel Babu]

Hello,

## Highlights
* If you pushed a patch today or did "recheck centos", please do a recheck.
Those jobs were not triggered.
* Please actually verify that the jobs for your patches have started. You
can do that by visiting https://build.gluster.org/job/smoke/ (for smoke) or
https://build.gluster.org/job/centos6-regression/ (for regression) and
searching for your review. Verify that the patchset is correct.

## The Details

This morning I installed critical security updates for Jenkins that needed
a restart of Jenkins. After this restart, it appears that the Gerrit plugin
failed to load because of an XML error in the config file. As far as I
know, this error has always existed, but the newer version of the plugin
became more strict in xml parsing. I noticed this only about an hour so ago
and I've fixed it. Please let me know if there are further problems. Due to
this any jobs that should have been triggered since about 8:30 am this
morning were not triggered. Please manually do a recheck for your patches.

Additionally, Ravi and Nithya pointed me to a problem where Gerrit wasn't
responding. We've noticed this quite often because we've configured Gerrit
to not drop idle connections. This forces us to restart Gerrit when there
are too many long-running idle connections. I've put a timeout of 10 mins
for idle connections. This issue should be sorted.

However, Jenkins does an SSH connection with Gerrit by running `ssh
jenk...@review.gluster.org stream-events`. I'm not sure if this Gerrit
config change will cause a conflict with Jenkins, but we'll see in the next
few hours. None of the documentation explicitly points to a problem.

-- 
nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra