Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: amazon-ecs-plugin
    • Labels:
      None
    • Environment:
      Ubuntu 16.04.3 LTS
      Oracle Java 1.8.0_131
      Jenkins 2.75
      amazon-ecs-plugin 1.11
    • Similar Issues:

      Description

      After configuring a ECS cluster named docker-cluster1 in AWS and also configuring the amazon-ecs-plugin to use it, I get this error in the jenkins.log:

      INFO: Started provisioning ECS Slave docker from aws-ecs with 1 executors. Remaining excess workload: 0
      Sep 26, 2017 12:32:48 PM hudson.slaves.NodeProvisioner$2 run
      WARNING: Unexpected exception encountered while provisioning agent ECS Slave docker
      com.amazonaws.services.ecs.model.ClusterNotFoundException: Cluster not found. (Service: AmazonECS; Status Code: 400; Error Code: ClusterNotFoundException; Request ID: f7bc84e2-a2a5-11e7-801f-1bbc4489a697)

       

      The error makes no sense as the plugin does autodetect the cluster and fills it in the dropdown in the Manage Jenkins interface (so there's no manual input error possible...).

       

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              roehrijn2 Jan Roehrich
              Reporter:
              ccaraivan Costin Caraivan
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: