We verified that the cacert with the correct serial number is trusted in the cacerts that is used by the Java JRE in which Jenkins run. I guess maybe it could still be in a CRL somewhere?
-Jimmy On Wednesday, 4 March 2015 16:57:06 UTC-5, Jimmy Ray wrote: > > One of our admins performed a YUM update on our AWS Linux Jenkins serve. > CA Certs were updated as well as Jenkins. Now existing Jobs are failing > and when we try to configure jobs with existing GitHub creds, we get the > following errors in Jenkins: > > Failed to connect to repository : Command "git ls-remote -h > <SOME_GIT_REPO> HEAD" returned status code 128: > stdout: > stderr: fatal: unable to access '<SOME_GIT_REPO>': Peer's certificate > issuer has been marked as not trusted by the user. > > We have verified that the cacerts used by Java were updated via YUM. Was > there a change to how Jenkins uses these certs from the Java JRE? Anyone > else seen this issue? > > -Jimmy > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bcfe7741-4fd5-43b5-94b6-4c318b819929%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
