Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Deployment is getting failed

0

We are trying to build and deploy dotnet application on windows platform in elastic beanstalk environment but deployment is getting failed with an error "Deployment completed, but with errors: During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. Failed to deploy application. Unsuccessful command execution on instance id(s) 'i-0031f3decb3972a8f'. Aborting the operation. [Instance: i-0031f3decb3972a8f ConfigSet: Infra-WriteRuntimeConfig, Infra-EmbeddedPreBuild, Hook-PreAppDeploy, Infra-EmbeddedPostBuild, Hook-EnactAppDeploy, Hook-PostAppDeploy] Command failed on instance. Return code: 1 Output: null. Deployment Failed: Unexpected Exception Error occurred during build: Command hooks failed"

Topics
DevOps.NET on AWSComputeDeveloper Tools
Tags
AWS CodeDeployDevOps.NET on AWSAWS CodePipelineAWS Elastic Beanstalk
Language
English
asked 3 years ago4.6K views
2 Answers
0

Hello there,

Looking into the error message, it seems like the command execution on the instances have failed. This can happen due to multiple reasons. At the end, it is mentioned that command hooks failed. If you are using hooks with the Elastic Beanstalk environment they might be failing too.

The best way to identify the reason behind the error is to fetch the logs of the environment or RDP into the instance. You need to look at the log locations to find the reason behind it. You can use this document to fetch the logs - https://repost.aws/knowledge-center/elastic-beanstalk-windows-instance-logs

If you are still not able to find the cause behind the issue, I request you to reach out to the Technical Support team with the environment ID and region for further investigation of the issue.

AWS
SUPPORT ENGINEER
answered 3 years ago
  • rePost-User-1875604
    3 years ago

    Thanks for your support.

  • Serlio
    2 years ago

    Did you ever find out how to overcome this issue? We're having the same issue and are looking for a solution. Please let us know if you found one. Thank you!

0

I also had this issue. What I found out was that when I upload the code through the AWS Toolkit in Visual Studio it worked. I noticed that the Extension deployes the published content directly into the zip e.g. 'release.zip' and when I publish/release my code through CI/CD pipelines it would have created a extra directory in the zip file. When I removed this extra directory I was able to upload my .net app again.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content