Enterprise Multiserver fails at AppASG and StreamASG upon CloudFormation Update

[ikenichiro]

Description
Updating an Enterprise Multiserver stack fails for AppASG and StreamASG because of timeout.
It is partially reported in #6002 and #6004 as also, but those issue also include a different issue so I'm reporting a new issue specific to this problem,

To Reproduce
Steps to reproduce the behavior:

1. Setup a working v1.1.5 stack (My Region is at Asia Pacific, ap-northeast-1), check everything is working, and then update the stack to offline mode from CloudFormation stack update function.
2. Make the CloudFormation stack to online, have the number of app servers and number of voice/videos streaming servers with the value more than 1.
3. Update the stack and wait until the resource creation,
4. AppASG and StreamASG stops at UPDATE_IN_PROGRESS after creating new instance and waiting for signal(s), wait for 30 minutes and see error.

Expected behavior
Have the CloudFormation stack to complete the update and show UPDATE_COMPLETE, accessible hubs cloud running on AWS.

Screenshots

Hardware

• Device: Desktop
• OS: Windows 10
• Browser: Firefox 111.0.0, 111.0.1

Additional context

• AWS Region: ap-northeast-1 (Tokyo)
• Hubs Cloud: No customization, including no custom client.
• The values for number of servers seems not to affect anything, I've tried up to 1 to 3 servers but it always fails with 0 SUCCESS

Things I have tried but did not work

• Try only with application server (0 for stream)
• Change EC2 instance type (c5.large, c5.xlarge)
• Change Load Balancing Method to DNS Round Robin

[NigelRidderhof]

I'm also running into these issues. Don't have much to bring into the conversation besides that it seems to me that multiple people are running into this around the same time. Maybe that could suggest there's something out of our reach that has changed? Not sure, just throwing it out there.

Personally hoping the Hubs team can reproduce it soon.

[eyesnareinc]

OK, it happened again with a NEW Stack. I just tried to update a new stack (moving it from offline to online). The stack updated seemed to stall in UPDATE_IN_PROGRESS and eventually the updated failed at AppASG.

[eyesnareinc]

Stack update failed (moving the stack from offline to online) for the brand new backup stack. I would love to find out why this is happening.

[pattersonbl2]

A workaround for this issue has been pinned to the top of the discussions page.

[FrankAllanRJ]

Where? I haven't found it yet.

Best regards

[FrankAllanRJ]

I still can't rewire my stack.
StreamASG | UPDATE_FAILED | Received 0 SUCCESS signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
#6063 (reply in thread)