Lori,
Somehow it seems to be better now. I just looked for the first time today and
the queue is only ~40
I wonder if we lost a bunch of jobs somehow?
JamO
On 11/28/2016 02:41 AM, Lori Jakab wrote:
> Hi,
>
> Just an FYI, the Jenkins queue is currently at over 500 entries, so jobs may
>
Lori,
Somehow it seems to be better now. I just looked for the first time today and
the queue is only ~40
I wonder if we lost a bunch of jobs somehow?
JamO
On 11/28/2016 02:41 AM, Lori Jakab wrote:
> Hi,
>
> Just an FYI, the Jenkins queue is currently at over 500 entries, so jobs may
>
Hi,
It seems that the Jenkins sandbox hasn't recovered from the maintenance,
possibly something needs to be cleared.
It looks like there are no executors in use but when trying to boot we get an
exception due to Quota exceeded [1], as if 250 instances are already in use.
Please update once
Well, we had a few jobs fail with "java.util.concurrent.ExecutionException:
org.jclouds.rest.AuthorizationException: {"forbidden": {"message": "Quota
exceeded for instances: Requested 1, but already used 250 of 250
instances", "code": 403}}". Not sure about lost jobs though...
On Mon, Nov 28,
Well, we had a few jobs fail with "java.util.concurrent.ExecutionException:
org.jclouds.rest.AuthorizationException: {"forbidden": {"message": "Quota
exceeded for instances: Requested 1, but already used 250 of 250
instances", "code": 403}}". Not sure about lost jobs though...
On Mon, Nov 28,
On Mon Nov 28 11:39:58 2016, lorand.jakab+...@gmail.com wrote:
> Well, we had a few jobs fail with "java.util.concurrent.ExecutionException:
> org.jclouds.rest.AuthorizationException: {"forbidden": {"message": "Quota
> exceeded for instances: Requested 1, but already used 250 of 250
> instances",
Hi,
Just an FYI, the Jenkins queue is currently at over 500 entries, so jobs
may take a while, can someone please take a look?
Thanks,
-Lori
___
infrastructure mailing list
infrastructure@lists.opendaylight.org
Hi,
I am going to auto answer to my original mail because I was wrong. The issue is
not due to the ovs-dpdk, it is related to an DHCP feature that we are
internally added to our ODL flavor (something already ported to the community)
and for such reason we are disabling the neutron dhcp
