Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
RedaBenh opened this issue Aug 23, 2017 · 8 comments

Comments

@RedaBenh
Copy link

RedaBenh commented Aug 23, 2017

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 RedaBenh changed the title error on stack cretaion (cloudformation) error on stack cretaion (cloudformation) "Failed to receive 1 resource signal(s) for the current batch" Aug 23, 2017
@mhart
Copy link
Member

mhart commented Aug 23, 2017

@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?

@RedaBenh
Copy link
Author

RedaBenh commented Aug 23, 2017

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
Copy link
Author

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

@mhart
Copy link
Member

mhart commented Aug 23, 2017

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

@RedaBenh
Copy link
Author

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 RedaBenh changed the title error on stack cretaion (cloudformation) "Failed to receive 1 resource signal(s) for the current batch" error on stack creation (cloudformation) "Failed to receive 1 resource signal(s) for the current batch" Aug 24, 2017
@shashank-6777
Copy link

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 ?

@dsreddy99
Copy link

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

@TsPuujee
Copy link

TsPuujee commented Jan 4, 2023

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" ... } }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants