So it turns out that this is a long-standing issue that Allen Wittenauer raised over a month ago in INFRA-11920, but which remains unresolved because of the notoriously thin resources in ASF Infra. To avoid reds in the mean time, can a committer go into the Jenkins jobs and just disable builds from getting tied to the solaris1 slave?
-Dima On Thu, Jun 23, 2016 at 1:00 PM, Dima Spivak <[email protected]> wrote: > Opened INFRA-12166 to see if ASF Infra can do something to certs on this > slave or if we’ll just need to have someone go into all our jobs and > exclude building on it manually. > > -Dima > > On Thu, Jun 23, 2016 at 11:26 AM, Mikhail Antonov <[email protected]> > wrote: > >> Oh, please do. Thanks for digging into it! >> >> On Thu, Jun 23, 2016 at 11:18 AM, Dima Spivak <[email protected]> >> wrote: >> >> > Looks like it’s only hitting one particular Jenkins slave (solaris1). >> The >> > builds around it that were kicked off on different machines were fine. I >> > can open an INFRA JIRA (unless you’d like to, Mikhail). >> > >> > -Dima >> > >> > On Thu, Jun 23, 2016 at 10:51 AM, Mikhail Antonov <[email protected]> >> > wrote: >> > >> > > Just saw that on several 1.4 builds - >> > > >> > > Caused by: hudson.plugins.git.GitException >> > > < >> > > >> > >> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException >> > > >: >> > > Command "/opt/csw/bin/git -c core.askpass=true fetch --tags --progress >> > > https://git-wip-us.apache.org/repos/asf/hbase.git >> > > +refs/heads/*:refs/remotes/origin/*" returned status code 128: >> > > stdout: >> > > stderr: fatal: unable to access >> > > 'https://git-wip-us.apache.org/repos/asf/hbase.git/': SSL certificate >> > > problem: unable to get local issuer certificate >> > > >> > > >> > > -Mikhail >> > > >> > >> >> >> >> -- >> Thanks, >> Michael Antonov >> > >
