Closed DGaffneyDC closed 7 years ago
This was a very simple solution which, for some reason, clicked only after posting this issue. While I previously was deploying to a load balanced elastic beanstalk app, changing the app config to "single instance" meant that the deployment failed the zero-downtime check. Unchecking the checkbox was all it took to solve this issue.
Perhaps another cup of coffee is in order.
Not sure where this is error is coming from. I've made sure to validate my credentials and the application/environment during config. The s3 bucket is properly identified as well. I dug into the stacktrace (below), and it looks like it's unable to find the environment even though it's already been validated. The beanstalk env is already running a previous version of the app, it's of the webServer tier, and the version labels are all based on jenkins build #, so none of the errors on the first level should apply. Any thoughts?