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

AWS SDK :: All 1.12.246-349 depends on unavailable AWS SDK :: Elastic Beanstalk 1.12.246-349

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • aws-java-sdk-plugin
    • None
    • Jenkins 2.346.1 on Amazon Linux 2

      aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c  released on June 22, 2022 requires at least version 1.12.246-349.v96b_b_f7eb_a_c3c of the aws-java-sdk-elasticbeanstalk module. However, the version of the aws-java-sdk-elasticbeanstalk module released on June 22 is 1.12.215-343.v953e693f0e86. I suspect that the elasticbeanstalk module was deployed with the incorrect version but am not familiar enough with the deploy process to understand why.

      The following is the text of the error when loading the plugin:

      Failed to load: Amazon Web Services SDK :: All (aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c)
       - Update required: Amazon Web Services SDK :: Elastic Beanstalk (aws-java-sdk-elasticbeanstalk 1.12.215-343.v953e693f0e86) to be updated to 1.12.246-349.v96b_b_f7eb_a_c3c or higher 

          [JENKINS-68834] AWS SDK :: All 1.12.246-349 depends on unavailable AWS SDK :: Elastic Beanstalk 1.12.246-349

          Nick Stevens created issue -
          Nick Stevens made changes -
          Description Original: {{aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c}}  released on June 22, 2022 requires at least version {{1.12.246-349.v96b_b_f7eb_a_c3c }}of the {{aws-java-sdk-elasticbeanstalk }}module. However, the version of the {{aws-java-sdk-elasticbeanstalk}} module released on June 22 is {{1.12.215-343.v953e693f0e86.}} I suspect that the elasticbeanstalk module was deployed with the incorrect version but am not familiar enough with the deploy process to understand why.

          The following is the text of the error when loading the plugin:
          {code:java}
          Failed to load: Amazon Web Services SDK :: All (aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c)
           - Update required: Amazon Web Services SDK :: Elastic Beanstalk (aws-java-sdk-elasticbeanstalk 1.12.215-343.v953e693f0e86) to be updated to 1.12.246-349.v96b_b_f7eb_a_c3c or higher {code}
          New: {{aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c}}  released on June 22, 2022 requires at least version {{1.12.246-349.v96b_b_f7eb_a_c3c}} of the {{aws-java-sdk-elasticbeanstalk}} module. However, the version of the {{aws-java-sdk-elasticbeanstalk}} module released on June 22 is {{1.12.215-343.v953e693f0e86}}. I suspect that the elasticbeanstalk module was deployed with the incorrect version but am not familiar enough with the deploy process to understand why.

          The following is the text of the error when loading the plugin:
          {code}
          Failed to load: Amazon Web Services SDK :: All (aws-java-sdk 1.12.246-349.v96b_b_f7eb_a_c3c)
           - Update required: Amazon Web Services SDK :: Elastic Beanstalk (aws-java-sdk-elasticbeanstalk 1.12.215-343.v953e693f0e86) to be updated to 1.12.246-349.v96b_b_f7eb_a_c3c or higher {code}
          Mariano Benes made changes -
          Attachment New: image-2022-06-24-18-31-31-679.png [ 58273 ]

          Mariano Benes added a comment -

          I'm having the same issue and since I can't login using withAWS it's blocking our deployments

           

          Mariano Benes added a comment - I'm having the same issue and since I can't login using withAWS it's blocking our deployments  

          Mariano Benes added a comment - - edited

          stevenna you can manually install the needed version of elastic beanstalk using this hpi, that should fix your problem while they work on the solution

          https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/aws-java-sdk/aws-java-sdk-elasticbeanstalk/1.12.246-349.v96b_b_f7eb_a_c3c/aws-java-sdk-elasticbeanstalk-1.12.246-349.v96b_b_f7eb_a_c3c.hpi

          Mariano Benes added a comment - - edited stevenna you can manually install the needed version of elastic beanstalk using this hpi, that should fix your problem while they work on the solution https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/aws-java-sdk/aws-java-sdk-elasticbeanstalk/1.12.246-349.v96b_b_f7eb_a_c3c/aws-java-sdk-elasticbeanstalk-1.12.246-349.v96b_b_f7eb_a_c3c.hpi

          Eloy Lafuente added a comment -

          Thanks griefwar,

          I can confirm that, with the elastic beanstalk version linked above the dependencies problems are gone. Going to run a few jobs to see if everything works as expected.

          Ciao

          Eloy Lafuente added a comment - Thanks griefwar , I can confirm that, with the elastic beanstalk version linked above the dependencies problems are gone. Going to run a few jobs to see if everything works as expected. Ciao

          Yi Gong added a comment -

          Will release a new version to fix this issue?

          Yi Gong added a comment - Will release a new version to fix this issue?

          Mark Waite added a comment - - edited

          https://github.com/jenkins-infra/helpdesk/issues/3019 describes the issue that you're seeing. The Jenkins update center data is updated every few minutes from a cached copy of all the Jenkins plugins and their versions. The combination of artifact ID and version number that is used by the most recent release of the AWS elastic beanstalk SDK plugin exceeded the limits of the caching mechanism that is currently being used. That stopped update center data refreshes for all users.

          https://github.com/jenkins-infra/update-center2/pull/606 implements a short term workaround to allow update center data refreshes to continue over the weekend. That short term workaround blocks the distribution of the most recent release of the AWS elastic beanstalk plugin so that other Jenkins users can continue to receive update center data refreshes.

          Further work is expected early next week to allow the update center to again distribute the most recent release of the AWS elastic beanstalk SDK plugin.

          In the interim, users can download the plugin from the Jenkins artifact repository.

          Mark Waite added a comment - - edited https://github.com/jenkins-infra/helpdesk/issues/3019 describes the issue that you're seeing. The Jenkins update center data is updated every few minutes from a cached copy of all the Jenkins plugins and their versions. The combination of artifact ID and version number that is used by the most recent release of the AWS elastic beanstalk SDK plugin exceeded the limits of the caching mechanism that is currently being used. That stopped update center data refreshes for all users. https://github.com/jenkins-infra/update-center2/pull/606 implements a short term workaround to allow update center data refreshes to continue over the weekend. That short term workaround blocks the distribution of the most recent release of the AWS elastic beanstalk plugin so that other Jenkins users can continue to receive update center data refreshes. Further work is expected early next week to allow the update center to again distribute the most recent release of the AWS elastic beanstalk SDK plugin. In the interim, users can download the plugin from the Jenkins artifact repository.
          Mark Waite made changes -
          Remote Link New: This issue links to "Jenkins infra help desk issue 3019 - artifact + version string too long (Web Link)" [ 27877 ]
          Mark Waite made changes -
          Remote Link New: This issue links to "Update center PR 606 - exclude release 1.12.246-349.v96b_b_f7eb_a_c3c (Web Link)" [ 27878 ]

            vlatombe Vincent Latombe
            stevenna Nick Stevens
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: