Open bigbitbus opened 5 years ago
Update: new day new behavior! Today the exact same commands worked (no reboot/ssh time issue); definitely may be worth parameterizing that timeout given the unknown reboot times of public cloud providers.
ubuntu@ip-172-26-2-212:~/go/bin$ ltops deploy --cluster mm-1 --mattermost master --license /home/ubuntu/mm/license.txt
INFO[0000] resolved master to https://releases.mattermost.com/mattermost-platform/master/mattermost-enterprise-linux-amd64.tar.gz
INFO[0000] deploying to proxy0 instance=ec2-3-83-65-247.compute-1.amazonaws.com
INFO[0027] deploying to app0 instance=ec2-34-203-227-251.compute-1.amazonaws.com
INFO[0053] successfully deployed to proxy0 instance=ec2-3-83-65-247.compute-1.amazonaws.com
INFO[0096] successfully deployed to app0 instance=ec2-34-203-227-251.compute-1.amazonaws.com
Hi
I am trying the setup the AWS terraform load testing rig.
I have successfully deployed the VMs and database (Terraform created them); but I cannot pass the stage when the app server is rebooted during the deploy time. Complains after 60s that VM is not available. I can ssh into the app server from the cli so its not a network/firewall issue.
Any way of making ltops waiting longer before giving up on ssh while the app server is booting?
I did grep this in the code
Would be nice to have a cli parameter for slow AWS reboot days perhaps?
Relevant logs: