search

docker-archive / for-aws

92 stars 26 forks source link

CF templates 17.12 to 18.03 doesn't work with minimal configuration, only one manager and one worker #162

Open ron72no opened 6 years ago

ron72no commented 6 years ago

Expected behavior

Create requested EC2 instances like 17.09 template did

Actual behavior

Permanent ROLLBACKs, no upgrade to newer docker version possible

Information

21:40:43 UTC+0200 ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack Docker-18-03 The following resource(s) failed to create: [ManagerAsg]. . Rollback requested by user.
  21:40:42 UTC+0200 CREATE_FAILED AWS::AutoScaling::AutoScalingGroup ManagerAsg Received 0 SUCCESS signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
  21:40:42 UTC+0200 UPDATE_IN_PROGRESS AWS::AutoScaling::AutoScalingGroup ManagerAsg Failed to receive 1 resource signal(s) for the current batch. Each resource signal timeout is counted as a FAILURE.
  21:20:40 UTC+0200 CREATE_IN_PROGRESS AWS::AutoScaling::AutoScalingGroup ManagerAsg Resource creation Initiated

Unable to satisfy 100% MinSuccessfulInstancesPercent requirement Failed to receive 1 resource signal(s) for the current batch. Each resource signal timeout is counted as a FAILURE.

Steps to reproduce the behavior

Create stack with CF templates >= 17.12. Choose 1 manager and 1 worker. Nothing else need to be changed within the wizard steps. No problems with the old 17.09 CF template.

swolf91 commented 6 years ago

I've the same problem for 3 managers and 2 workers:

2018-07-20 Status Type Logical ID Status Reason
12:11:58 UTC+0200 CREATE_FAILED AWS::AutoScaling::AutoScalingGroup ManagerAsg Received 0 SUCCESS signal(s) out of 3. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
12:11:57 UTC+0200 UPDATE_IN_PROGRESS AWS::AutoScaling::AutoScalingGroup ManagerAsg Failed to receive 3 resource signal(s) for the current batch. Each resource signal timeout is counted as a FAILURE.
swolf91 commented 6 years ago

Okay the problem seems to be related to the "Enable EBS I/O optimization?" setting. Enabling the option causes the error. If I disable it, everything works quite fine.

dsikes commented 4 years ago

@boeserwolf91 Thanks! That was the issue I had as well.