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

JClouds plugin fails on Jenkins v2.28

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • jclouds-plugin
    • None

      We use the JClouds plugin to provision OpenNebula instances via aws-ec2 api
      Since update to 2.28 the connection fails.

      From the stack trace i guess this is related to JENKINS-38736

      Cannot connect to specified cloud, please check the identity and credentials: Unable to create injector, see the following errors:

      1) Overriding @Provides methods is not allowed.
      @Provides method: org.jclouds.logging.config.LoggingModule.createLoggerFactory()
      overridden by: jenkins.plugins.jclouds.compute.JCloudsCloud$1.createLoggerFactory()
      at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163)

      2) Overriding @Provides methods is not allowed.
      @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideTemplateOptions()
      overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideTemplateOptions()
      at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163)

      3) Overriding @Provides methods is not allowed.
      @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideImageExtension()
      overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideImageExtension()
      at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163)

      4) Overriding @Provides methods is not allowed.
      @Provides method: org.jclouds.compute.config.BaseComputeServiceContextModule.provideSecurityGroupExtension()
      overridden by: org.jclouds.aws.ec2.compute.config.AWSEC2ComputeServiceContextModule.provideSecurityGroupExtension()
      at com.google.inject.internal.ProviderMethodsModule.getProviderMethods(ProviderMethodsModule.java:163)

          [JENKINS-39505] JClouds plugin fails on Jenkins v2.28

          Georg Brunmayr created issue -
          Bernd Farka made changes -
          Link New: This issue relates to JENKINS-38736 [ JENKINS-38736 ]

          Fritz Elfert added a comment -

          Which version of the jclouds plugin are you using? (From the plugins page or built from git).

          Fritz Elfert added a comment - Which version of the jclouds plugin are you using? (From the plugins page or built from git).

          Bernd Farka added a comment -

          The Version Form the Plugin page

          Bernd Farka added a comment - The Version Form the Plugin page

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Fritz Elfert
          Path:
          jclouds-plugin/pom.xml
          pom.xml
          http://jenkins-ci.org/commit/jclouds-plugin/2af5ce412ccb79e70e26a6eab82e6e8ca0049eb4
          Log:
          Attempt to fix JENKINS-39505

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml pom.xml http://jenkins-ci.org/commit/jclouds-plugin/2af5ce412ccb79e70e26a6eab82e6e8ca0049eb4 Log: Attempt to fix JENKINS-39505

          Bernd Farka added a comment -

          If I can hell you verifying something just let me know...

          Bernd Farka added a comment - If I can hell you verifying something just let me know...

          Fritz Elfert added a comment - - edited

          I have just made a commit to https://github.com/jenkinsci/jclouds-plugin which should fix your problem.
          Are you able to build this yourself or do you need an installable .hpi?
          If you need an installable .hpi, please contact me privately via email.
          ATTENTION-ATTENTION-ATTENTION
          BEFORE updating, be shure to backup your your <jenkins-homedir>/config.xml and <jenkins-homedir>/credentials.xml !!!!!
          Reason: The new plugin uses jenkins credentials framework and auto-migrates any old jclouds-credentials into the new credential-system.
          If you want to go downgrade for some reason, you must downgrade the plugin, then stop jenkins and copy the backup over the existing xmls
          After that, you can start jenkins again and should have the old configuration.

          Fritz Elfert added a comment - - edited I have just made a commit to https://github.com/jenkinsci/jclouds-plugin which should fix your problem. Are you able to build this yourself or do you need an installable .hpi? If you need an installable .hpi, please contact me privately via email. ATTENTION-ATTENTION-ATTENTION BEFORE updating, be shure to backup your your <jenkins-homedir>/config.xml and <jenkins-homedir>/credentials.xml !!!!! Reason: The new plugin uses jenkins credentials framework and auto-migrates any old jclouds-credentials into the new credential-system. If you want to go downgrade for some reason, you must downgrade the plugin, then stop jenkins and copy the backup over the existing xmls After that, you can start jenkins again and should have the old configuration.

          Fritz Elfert added a comment -

          Correction: The latest build artifact is also available here: https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/ws/jclouds-plugin/target/jclouds-jenkins.hpi

          Fritz Elfert added a comment - Correction: The latest build artifact is also available here: https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/ws/jclouds-plugin/target/jclouds-jenkins.hpi

          Daniel Beck added a comment -

          Is this actually related to JENKINS-38736 ?

          Daniel Beck added a comment - Is this actually related to JENKINS-38736 ?

          Fritz Elfert added a comment - - edited

          Indirectly yes. The well known classloader isolation problem. The jclouds libs depend on an older guice and some other conflicting libs.
          As a developer, I was always struggling with that. It is also the reason why a shaded jclouds lib is included in the plugin.
          However, I was able to fix this by enabling the pluginFirstClassLoader.

          -Fritz

          Fritz Elfert added a comment - - edited Indirectly yes. The well known classloader isolation problem. The jclouds libs depend on an older guice and some other conflicting libs. As a developer, I was always struggling with that. It is also the reason why a shaded jclouds lib is included in the plugin. However, I was able to fix this by enabling the pluginFirstClassLoader. -Fritz

            felfert Fritz Elfert
            brunmayr Georg Brunmayr
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: