ecs icon indicating copy to clipboard operation
ecs copied to clipboard

error on stack creation (cloudformation) "Failed to receive 1 resource signal(s) for the current batch"

Open RedaBenh opened this issue 8 years ago • 8 comments

i get this error when i try to create the stack in cloudformation

Failed to receive 1 resource signal(s) for the current batch, Each resource signal timeout is counted as a FAILURE

image

RedaBenh avatar Aug 23 '17 13:08 RedaBenh

@RedaBenh bit strange – doesn't really tell you what the problem was aside from the fact that the EC2 instance didn't start up within 5 minutes.

Maybe just try again and see what happens?

mhart avatar Aug 23 '17 13:08 mhart

thanks @mhart for your answer,

I try again but i get the same issue finally, i create the stack by changing ResourceSignal:Count


...
  "Resources": {
    ...
    "AutoScalingGroup": {
    ...
      "CreationPolicy": {
        "ResourceSignal": {
          "Count": "0"
        }
      }

    }
    ...

but now i get another error during my build No Container Instances were found in your cluster.

here is the content of my package.json

{
  "name": "Test-repo---4cb9",
  "lambci": {
    "cmd": "npm -v",
    "docker": {
      "cluster": "lambci-ecs-Test-Cluster-X3TSS7RPOQAO",
      "task": "lambci-ecs-Test-BuildTask-8TSNV9QV4GXF"
    }
  }
}

RedaBenh avatar Aug 23 '17 14:08 RedaBenh

i get more details of this error in the autoscaling group activities image

RedaBenh avatar Aug 23 '17 14:08 RedaBenh

Ah ok, this is a duplicate of #7

You should be able to create a default VPC to get around this:

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html

The other options are changing the instance type in the template, or you can have a look at this PR:

https://github.com/lambci/ecs/pull/6/files

At the moment there are too many changes in there to merge, but you might be able to find a solution

mhart avatar Aug 23 '17 14:08 mhart

i try both solutions: 1- Configure a private VPC 2- Use the @droidlabour 's template in the PR #6 But i always the message: No Container Instances were found in your cluster.

RedaBenh avatar Aug 24 '17 10:08 RedaBenh

Hi All,

Am getting same error, Can anyone tell me what should i change and exactly where. Environment:- Am trying to deploy redhat openshift over AWS using default template.

Please help ?

shashank-6777 avatar Mar 09 '19 04:03 shashank-6777

The Cfn-Signal is not routing back to the cloud-formation Endpoint. Please try to check the instance access to the internet or nat gateway. If the instance are in the private subnet, make sure the endpoints are properly configured

dsreddy99 avatar Jul 27 '20 10:07 dsreddy99

remove creation policy and update policy { "WebServerGroup": { "Type": "AWS::AutoScaling::AutoScalingGroup", "CreationPolicy": { "ResourceSignal": { "Timeout": "PT15M", "Count": "1" } }, "UpdatePolicy": { "AutoScalingRollingUpdate": { "MinInstancesInService": "1", "MaxBatchSize": "1", "PauseTime": "PT15M", "WaitOnResourceSignals": "true" } }, "Properties": { "AutoScalingGroupName": "super-asg" ... } } }

after of remove and my running template is "WebServerGroup": { "Properties": { "AutoScalingGroupName": "super-asg" ... } }

TsPuujee avatar Jan 04 '23 00:01 TsPuujee