search

ingenieux / awseb-deployment-plugin

Jenkins Plugin for AWS Elastic Beanstalk
Apache License 2.0
29 stars 53 forks source link

DeploymentFailed : Environment Update timed-out. Aborting. #55

Closed prkrkmr closed 7 years ago

prkrkmr commented 7 years ago

Hello Sir I am getting this error everytime for a jenkins job I set up Environment Update timed-out. Aborting. Even when the application is updating and is successfully after some time. The deployment strategy for that beanstalk application is set to rolling updates and has more than one instance. Can you please tell me if the timed-out is being caused by the presence of multiple instances or because of the rolling updates or any other reason. Thanks in advance.

aldrinleal commented 7 years ago

very likely, its your AWS Elastic Beanstalk application / configuration. Look into the application logs on the AWS Console and/or the retrieve-environment-info command:

http://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/retrieve-environment-info.html

prkrkmr commented 7 years ago

Thank you for the quick reply. Please allow me to be more specific, the application update at the AWS Elastic beanstalk update is always successful, it is the jenkins job which times out and marks the jenkins builld as failure, even when the AWS application is successfully deployed after some time. Can you please tell me if I set up the option Ensure Health is Green after deploy? will it wait for the job to be finished at the AWS beanstalk end. Sorry to bother you about this. Thanks in advance.

aldrinleal commented 7 years ago

Paste the deployment logs please.

prkrkmr commented 7 years ago

issue

aldrinleal commented 7 years ago

Paste the deployment logs please (not screenshots)

pjrola commented 7 years ago

Was this ever resolved? I am experiencing the same issue.

aldrinleal commented 7 years ago

The OP didn't post the logs. If you want, you can post it here.

mgaeta commented 4 years ago 
AWSEB Deployment Plugin Version 0.3.15
Zippinf contents of Root File Object (###) into tmp file ### (inludes=, exludes=)
Uploading file ### as s3://###
Creating application version ### for application ### for path s3://###
Created version: ###
Using environmentId '###'
No pending Environment Updates. Proceeding.
Checking health/status of environmentId ### attempt 1/2
Environment Status is 'Ready'. Moving on.
Updating environmentId '###' with Version Label set to '###'
Checking health/status of environmentId ### attempt 1/2
Versions reported: (current=###), underDeployment: (###). Should I move on? false
Wed Feb 22 13:33:17 UTC 2017 [INFO] Environment health has transitioned from Ok to Info. Application update in progress on 1 instance. 0 out of 2 instances completed (running for 20 seconds).
Wed Feb 22 13:32:59 UTC 2017 [INFO] Batch 1: Starting application deployment command execution.
Wed Feb 22 13:32:41 UTC 2017 [INFO] Batch 1: De-registering instance(s) from the load balancer and waiting for them to go out of service.
Wed Feb 22 13:32:40 UTC 2017 [INFO] Batch 1: Starting application deployment on instance(s) [###].
Wed Feb 22 13:32:39 UTC 2017 [INFO] Deploy new version to instance(s).
Checking health/status of environmentId ### attempt 2/2
Versions reported: (current=###), underDeployment: (###). Should I move on? false
Environment Update timed-out. Aborting.
Cleaning up temporary file ###
Build setp 'AWS Elastic Beanstalk' marked build as failure
[PostBuildScript] - Execution post build scripts.
[PostBuildScript] Build is not success : do not execute script
Finished: FAILURE
aldrinleal commented 4 years ago

@mgaeta create a new case - with enough details, like the output of retrieve environment as mentioned.