Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40903

Server Name Indication is not supported

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When I try to build config-file-provider-plugin with a Nexus server set as proxy it fails with:

      12:37:13 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]
      12:37:13 Deleting 1 temporary files
      12:37:13 ERROR: Failed to parse POMs
      12:37:13 java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 13
      12:37:13 
      12:37:13 	at hudson.FilePath.act(FilePath.java:992)
      12:37:13 	at hudson.FilePath.act(FilePath.java:974)
      12:37:13 	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980)
      12:37:13 	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692)
      12:37:13 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
      12:37:13 	at hudson.model.Run.execute(Run.java:1728)
      12:37:13 	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)
      12:37:13 	at hudson.model.ResourceController.execute(ResourceController.java:98)
      12:37:13 	at hudson.model.Executor.run(Executor.java:404)
      12:37:13 Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 13
      12:37:13 
      12:37:13 	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1384)
      12:37:13 	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)
      12:37:13 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)
      12:37:13 	at hudson.remoting.UserRequest.perform(UserRequest.java:153)
      12:37:13 	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
      12:37:13 	at hudson.remoting.Request$2.run(Request.java:336)
      12:37:13 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      12:37:13 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
      12:37:13 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      12:37:13 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      12:37:13 	at java.lang.Thread.run(Thread.java:745)
      12:37:13 	at ......remote call to IQ-61a8ac47b316(Native Method)
      12:37:13 	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
      12:37:13 	at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
      12:37:13 	at hudson.remoting.Channel.call(Channel.java:822)
      12:37:13 	at hudson.FilePath.act(FilePath.java:985)
      12:37:13 	... 8 more
      12:37:13 Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 13
      12:37:13 
      12:37:13 	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
      12:37:13 	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
      12:37:13 	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
      12:37:13 	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1321)
      12:37:13 	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)
      12:37:13 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)
      12:37:13 	at hudson.remoting.UserRequest.perform(UserRequest.java:153)
      12:37:13 	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
      12:37:13 	at hudson.remoting.Request$2.run(Request.java:336)
      12:37:13 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      12:37:13 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
      12:37:13 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      12:37:13 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      12:37:13 	at java.lang.Thread.run(Thread.java:745)

      I think the maven-wagon ticket is here: https://issues.apache.org/jira/browse/WAGON-372
      Apache HTTP Client SNI: https://issues.apache.org/jira/browse/HTTPCLIENT-1119

      Maven Users thread: http://maven.40175.n5.nabble.com/maven-SNI-problems-td5802694.html

      Similiar to: JENKINS-26403

        Attachments

          Issue Links

            Activity

            Hide
            jbochenski Jakub Bochenski added a comment - - edited

            Workaround: change <mirrorOf>external:*</mirrorOf> to <mirrorOf>external:*,!repo.jenkins-ci.org</mirrorOf> in Maven settings

            Result is

            15:02:55 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]
            15:02:55 Downloaded artifact https://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/2.17/plugin-2.17.pom
            Show
            jbochenski Jakub Bochenski added a comment - - edited Workaround: change <mirrorOf>external:*</mirrorOf> to <mirrorOf>external:*,!repo.jenkins-ci.org</mirrorOf> in Maven settings Result is 15:02:55 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https: //readonly-mvnrepo.acme-internal.com/content/groups/ public /): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] 15:02:55 Downloaded artifact https: //repo.jenkins-ci.org/ public /org/jenkins-ci/plugins/plugin/2.17/plugin-2.17.pom
            Hide
            flungo Fabrizio Lungo added a comment -

            Having this same issue. It seems to be an SNI issue as the certificate I am getting is the one I would get accessing the IP without a hostname. This only seems to be an issue for getting the parent POM as the mirror is usable for proxying maven central.

            Show
            flungo Fabrizio Lungo added a comment - Having this same issue. It seems to be an SNI issue as the certificate I am getting is the one I would get accessing the IP without a hostname. This only seems to be an issue for getting the parent POM as the mirror is usable for proxying maven central.
            Hide
            aheritier Arnaud Héritier added a comment -

            In the next version 2.15 of the plugin we upgraded Wagon dependencies to their latest version.
            If the problem occurs when Jenkins does the "Parsing POM" I hope it should be fixed

            Show
            aheritier Arnaud Héritier added a comment - In the next version 2.15 of the plugin we upgraded Wagon dependencies to their latest version. If the problem occurs when Jenkins does the "Parsing POM" I hope it should be fixed
            Hide
            flungo Fabrizio Lungo added a comment -

            I can confirm that it is during the "Parsing POM" stage that the error occurs. I'll provide feedback once 2.15 is released. Thanks.

            Show
            flungo Fabrizio Lungo added a comment - I can confirm that it is during the "Parsing POM" stage that the error occurs. I'll provide feedback once 2.15 is released. Thanks.
            Hide
            aheritier Arnaud Héritier added a comment -

            FYI 2.15.1 is out

            Show
            aheritier Arnaud Héritier added a comment - FYI 2.15.1 is out
            Hide
            flungo Fabrizio Lungo added a comment -

            This is now working for me. Thanks.

            Show
            flungo Fabrizio Lungo added a comment - This is now working for me. Thanks.
            Hide
            aheritier Arnaud Héritier added a comment -

            great. Thanks for your feedback Fabrizio Lungo I will update 2.15 changelog to mark this as solved

            Show
            aheritier Arnaud Héritier added a comment - great. Thanks for your feedback Fabrizio Lungo I will update 2.15 changelog to mark this as solved
            Hide
            aheritier Arnaud Héritier added a comment -

            Solved in 2.15 with Wagon update

            Show
            aheritier Arnaud Héritier added a comment - Solved in 2.15 with Wagon update

              People

              • Assignee:
                aheritier Arnaud Héritier
                Reporter:
                jbochenski Jakub Bochenski
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: