On Wednesday 17 June 2015 04:23 PM, Niels de Vos wrote:
On Wed, Jun 17, 2015 at 09:56:32PM +0200, Emmanuel Dreyfus wrote:
Niels de Vos wrote:
Maybe, but I hope those issues stay masked when resolving the hostnames
is more stable. When we have the other servers up and running, we would
have a
On Wed, Jun 17, 2015 at 09:56:32PM +0200, Emmanuel Dreyfus wrote:
> Niels de Vos wrote:
>
> > Maybe, but I hope those issues stay masked when resolving the hostnames
> > is more stable. When we have the other servers up and running, we would
> > have a better understanding and options to investig
Niels de Vos wrote:
> Maybe, but I hope those issues stay masked when resolving the hostnames
> is more stable. When we have the other servers up and running, we would
> have a better understanding and options to investigate issues like this.
But Jenkins is still unable to launch an agent on e.g
On Wed, Jun 17, 2015 at 11:48:46AM +0200, Michael Scherer wrote:
> Le mercredi 17 juin 2015 à 08:20 +0200, Emmanuel Dreyfus a écrit :
> > Venky Shankar wrote:
> >
> > > If that's the case, then I'll vote for this even if it takes some time
> > > to get things in workable state.
> >
> > See my ot
Le mercredi 17 juin 2015 à 08:20 +0200, Emmanuel Dreyfus a écrit :
> Venky Shankar wrote:
>
> > If that's the case, then I'll vote for this even if it takes some time
> > to get things in workable state.
>
> See my other mail about this: you enter a new slave VM in the DNS and it
> does not reso
On Wed, Jun 17, 2015 at 11:48:46AM +0200, Michael Scherer wrote:
> And I think the DNS issues are just a symptom of a bigger network issue,
> having local DNS might just mask the problem and which would then be non
> DNS related ( like tcp connexion not working ).
Well, if it is lost packets, TCP
Venky Shankar wrote:
> If that's the case, then I'll vote for this even if it takes some time
> to get things in workable state.
See my other mail about this: you enter a new slave VM in the DNS and it
does not resolve, or somethimes you get 20s delays. I am convinced this
is the reason why Jenk
On Wed, Jun 17, 2015 at 10:13 AM, Emmanuel Dreyfus wrote:
> Atin Mukherjee wrote:
>
>> > That *might* result in lots of NetBSD regression failures later on and
>> > we may end up with another round of fixups.
>> Agreed, that's the known risk but we don't have any other alternatives atm.
>
> I str
Atin Mukherjee wrote:
> > That *might* result in lots of NetBSD regression failures later on and
> > we may end up with another round of fixups.
> Agreed, that's the known risk but we don't have any other alternatives atm.
I strongly disagree, we have a good alternative: configure a secondary
DN
On 06/17/2015 09:57 AM, Venky Shankar wrote:
> On Wed, Jun 17, 2015 at 9:50 AM, Atin Mukherjee wrote:
>>
>>
>> On 06/11/2015 08:04 PM, Emmanuel Dreyfus wrote:
>>> On Thu, Jun 11, 2015 at 04:04:44PM +0200, Niels de Vos wrote:
Michael installed and configured dnsmasq on build.gluster.org yest
On Wed, Jun 17, 2015 at 9:50 AM, Atin Mukherjee wrote:
>
>
> On 06/11/2015 08:04 PM, Emmanuel Dreyfus wrote:
>> On Thu, Jun 11, 2015 at 04:04:44PM +0200, Niels de Vos wrote:
>>> Michael installed and configured dnsmasq on build.gluster.org yesterday.
>>> If that does not help today, we need other
On 06/11/2015 08:04 PM, Emmanuel Dreyfus wrote:
> On Thu, Jun 11, 2015 at 04:04:44PM +0200, Niels de Vos wrote:
>> Michael installed and configured dnsmasq on build.gluster.org yesterday.
>> If that does not help today, we need other ideas...
>
> Just to confirm the problem:
>
> [manu@build ~]$
On Thu, Jun 11, 2015 at 04:04:44PM +0200, Niels de Vos wrote:
> Michael installed and configured dnsmasq on build.gluster.org yesterday.
> If that does not help today, we need other ideas...
Just to confirm the problem:
[manu@build ~]$ time nslookup nbslave7i.cloud.gluster.org
;; connection timed
On Thu, Jun 11, 2015 at 12:25:13PM +, Emmanuel Dreyfus wrote:
> On Thu, Jun 11, 2015 at 12:51:52PM +0200, Niels de Vos wrote:
> > I've just checked the online NetBSD slaves again, but they seem to have
> > been configured correctly... Maybe we are hitting a Jenkins bug, or
> > there was a (temp
On Thu, Jun 11, 2015 at 12:51:52PM +0200, Niels de Vos wrote:
> I've just checked the online NetBSD slaves again, but they seem to have
> been configured correctly... Maybe we are hitting a Jenkins bug, or
> there was a (temporary?) issue with DNS resolution?
DNS resolution is wrecked on build.glu
On Thu, Jun 11, 2015 at 09:48:22AM +, Emmanuel Dreyfus wrote:
> On Thu, Jun 11, 2015 at 07:26:00AM +, Emmanuel Dreyfus wrote:
> > In my opinion the fix to this problem is to start new VM. I was busy
> > on other fronts hence I did not watched the situation, but it is still
> > grim, with m
On Thu, Jun 11, 2015 at 07:26:00AM +, Emmanuel Dreyfus wrote:
> In my opinion the fix to this problem is to start new VM. I was busy
> on other fronts hence I did not watched the situation, but it is still
> grim, with most NetBSD slaves been in screwed state. We need to spin
> more.
Launchi
On Thu, Jun 11, 2015 at 12:39:43PM +0530, Atin Mukherjee wrote:
> Can we start merging patches with out NetBSD's vote? Currently we have
> so many patches waiting for NetBSD's vote and it seems like no vms are
> apparently running as well. This is blocking us to move forward.
In my opinion the fix
On 06/11/2015 09:31 AM, Avra Sengupta wrote:
> Hi,
>
> New patches being submitted are not getting NetBSD regressions run on
> them. Even manually they are not getting triggered. Is anyone aware of
> this?
Can we start merging patches with out NetBSD's vote? Currently we have
so many patches wai
Hi,
New patches being submitted are not getting NetBSD regressions run on
them. Even manually they are not getting triggered. Is anyone aware of this?
Regards,
Avra
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailm
20 matches
Mail list logo
