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

JClouds aws-ec2 always tries to use default subnet

    XMLWordPrintable

Details

    Description

      When manually assigning nodes to use a security group (SG) that is configured on a different virtual private cloud (VPC) during launch the plugin always tries to attach the node to default subnet, even when a vpc ID or subnet ID is specified in the networks option.

      This causes the instance to not be created since the requested subnet is not part of the SG.

      Attachments

        Activity

          trnubo Tim Robinson added a comment -

          I'm also seeing this issue on AWS. Also tested against a recent SNAPSHOT but got the same error.

          trnubo Tim Robinson added a comment - I'm also seeing this issue on AWS. Also tested against a recent SNAPSHOT but got the same error.
          grv87 Basil Peace added a comment -

          +1

          VPC setting is not honored. I got 'No default VPC for this user' error.

          grv87 Basil Peace added a comment - +1 VPC setting is not honored. I got 'No default VPC for this user' error.
          grv87 Basil Peace added a comment - Proposed fix:  https://github.com/jenkinsci/jclouds-plugin/pull/129

          I would really like to see this get fixed at some point. My team and I have been having to use the EC2 plugin to get around the failure of this one to operate as expected. That plugin is a lot less robust than JClouds and has required us to put a lot of brittle cron jobs in place to take care of things that this one natively supports.

          tykeal Andrew Grimberg added a comment - I would really like to see this get fixed at some point. My team and I have been having to use the EC2 plugin to get around the failure of this one to operate as expected. That plugin is a lot less robust than JClouds and has required us to put a lot of brittle cron jobs in place to take care of things that this one natively supports.
          felfert Fritz Elfert added a comment -

          Committed to master. Please test (I don't have an AWS account anymore)

          Will be released in 2.16. Sorry it took so long.

          felfert Fritz Elfert added a comment - Committed to master. Please test (I don't have an AWS account anymore) Will be released in 2.16. Sorry it took so long.
          felfert Fritz Elfert added a comment -

          Released in 2.16

          felfert Fritz Elfert added a comment - Released in 2.16

          People

            felfert Fritz Elfert
            tykeal Andrew Grimberg
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: