Hubs Multi Servier Template Update fails / No SES emails - Software Version 1.1.5

[standtech]

Description
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '[CloudFormation]'
2. Click on 'Update.'
3. Scroll down to ' No of app servers' or 'No of Steams servers'
4. change number
5. See error

In the events You see -

AppASG	UPDATE_IN_PROGRESS	New instance(s) added to autoscaling group - Waiting on 1 resource signal(s) with a timeout of PT30M.

StreamASG	UPDATE_IN_PROGRESS	New instance(s) added to autoscaling group - Waiting on 1 resource signal(s) with a timeout of PT30M.

And it fails / rolls back in the end .
That means we can not scale no of servers during the actual event . Same behaviour when I changed Admin email as well . So it looks like , anything which is an update will fail the deployment.

Another issue is , First time deployment works but Mails are not received which are required for admin login even though N.virginia has domain/email verified in SES ( in sandbox) so not able to login even after 9-10 attempts .
PS: Personal Edition worked without any hiccups .

Expected behavior

As per the documentation , it should scale . vertical or horizontal EC2 scaling. Allows administrator to tweak number and Ec2 types based on use case , Development scenario or Production events.

After Deployment, you browse admin console and key in Email ID configured. A link is send to you admin email and you click and validate authenticity to login on Admin console.

Screenshots
If applicable, add screenshots to help explain your problem.

Hardware

• Device: MacBook
• OS: MacBook has Monterey , on AWS , Default AWS AMIs bundled in template
• Browser: [Chrome/Safari )

Additional context
Add any other context about the problem here.

[SV-AndreiC]

I was able to successfully update a stack, adding extra instances while using a Windows machine. I was also running the vanilla Hubs Cloud on the stack.

Are u using a custom client or the vanilla version?

[standtech]

we are running Enterprise multi-server on AWS cloud using template . After many permutations and combinations, it seems it works with Root account but not with an account with full admin role assigned. So its either AWS Policy or cloudformation internal calls issue. Not much documentation around this or clear instructions.

[eyesnareinc]

I also encountered stalling (I think) with AppASG with the same Status reason message as above: "New instance(s) added to autoscaling group - Waiting on 1 resource signal(s) with a timeout of PT30M" The update resulted in a stack update fail. Update just was moving the stack offline to online. I tried to update multiple times and the stack failed to update and triggered UPDATE_ROLLBACK_COMPLETE each time. Then, I updated the template to Hubs Cloud Personal 1.1.5 (stack was offline) and the stack update failed at AppDb with the status reason "Cannot find upgrade target from 10.serverless_21 with requested version 11.13 for serverless engine mode." Rollback also failed.

[eyesnareinc]

[standtech]

I am doing Fresh installation and facing again same issue with Root account as well , no respite.
It's likes If it go through you are lucky , just keep trying . ;)

[SV-AndreiC]

@tanfarming Can u take a look, QA team was not able to reproduce this issue with the lastest HC version and the 1.1.5 template.

[standtech]

cleaned up EFS/RDS backups , route53 zone entries and redeployed fresh template using root account , am now getting "502 Bad Gateway" . Restart of Ec2 doesn't help . If I update cloudformation I would be wasting 30 minutes watching it to rollback . This is second attempt today . It worked well before I tried "change set" option and also after clicking on "stacks options" > "view in app manager " Not sure whats wrong ... Is there anything we shouldn't be doing ?

[standtech]

PS: We are using Amazon Linux AMIs through the Mozilla hubs software.

[standtech]

Tried few times more , both multi and single instance fresh install , am still getting "502 Bad Gateway" due to below issue .
Any "Update" to the template will fail with the same AppASG issue .

[standtech]

Installed Personal edition , after fresh install got black screen saying cloud is down , and when tried to update to turn off failed with the same issue.

[eyesnareinc]

Same error happened to me on 2 brand new stack builds. I am using the 1.1.5 template Hubs Cloud Personal with t3.medium EC2

[standtech]

Hello

When can we get some response here , seems product is not stable and impossible to deploy.

[standtech]

HELLO MOZILLA HUBS SUPPORT

ITS JUNE NOW , Could we have any response on this ?

Product is not a open source so expecting some resolution here...