On Wed Mar 13 08:05:35 2019, [email protected] wrote:
> On 13/03/2019 13:01, Robert Varga wrote:
> > Hello,
> >
> > it seems our cloud is experiencing issues:
> >
> > https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/bgpcep-
> > maven-verify-sodium-mvn35-openjdk8/30/console.log.gz:
> >
> >> [WARNING] Could not transfer metadata
> >> org.opendaylight.controller:odl-mdsal-trace:1.10.0-SNAPSHOT/maven-
> >> metadata.xml from/to opendaylight-snapshot
> >> (https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/):
> >> Failed to transfer file:
> >> https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/controller/odl-
> >> mdsal-trace/1.10.0-SNAPSHOT/maven-metadata.xml. Return code is: 502
> >> , ReasonPhrase:Bad Gateway.
> >> [WARNING] Failure to transfer org.opendaylight.controller:odl-mdsal-
> >> trace:1.10.0-SNAPSHOT/maven-metadata.xml from
> >> https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/
> >> was cached in the local repository, resolution will not be
> >> reattempted until the update interval of opendaylight-snapshot has
> >> elapsed or updates are forced. Original error: Could not transfer
> >> metadata org.opendaylight.controller:odl-mdsal-trace:1.10.0-
> >> SNAPSHOT/maven-metadata.xml from/to opendaylight-snapshot
> >> (https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/):
> >> Failed to transfer file:
> >> https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/controller/odl-
> >> mdsal-trace/1.10.0-SNAPSHOT/maven-metadata.xml. Return code is: 502
> >> , ReasonPhrase:Bad Gateway.
> >
> > Furthermore:
> >
> > 1) we do not have 4c-4g slaves:
> >
> > https://jenkins.opendaylight.org/releng/label/centos7-builder-4c-
> > 4g/load-statistics
> >
> 
> Same goes for 4c-16g slaves:
> 
> https://jenkins.opendaylight.org/releng/label/centos7-autorelease-4c-
> 16g/load-statistics
> 
> which means autorelease-sodium-openjdk11 #40 has been sitting there
> for
> more than 2 hours.
> 
> Regards,
> Robert

Hi Everyone,

We are actively looking into this issue. What we know now is that provisioning 
is timing out for all new minions. We've contacted our cloud provider and they 
are investigating on their end.

In the meantime I'm trying to clear out all the orphaned systems that are not 
attached to Jenkins. I've temporarily put Jenkins into shutdown mode so that we 
can clear out the systems.

Will update once we know more.

Regards,
Thanh


_______________________________________________
infrastructure mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/infrastructure

Reply via email to