How I fixed my Failed Elastic Beanstalk Deploy

So I’ve been messing around with AWS and figuring out all of the service offerings.

Recently, I noticed that deploy had been failing for awhile.

Screen Shot 2018-04-15 at 8.11.13 PM

I first added monitoring to the Elastic Beanstalk Deploy status so I wouldn’t continue to push code up without knowing if the deploy failed. This is how I did it.

I then looked at why it was failing. I think in the EB health status.

It said:

Incorrect application version found on all instances. Expected version “codepipeline-1522981381920-note-taking-app-Build Artifact-a394db38-54b8-4ec1-ab9a-e075a474b588” (deployment 8).

and I Google Searched a form of the error go get to better results “Incorrect application version found on all instances”

That search leads me to this AWS documentation.

From this documentation, I tried all the solutions offered:

To solve this issue, start another deployment. You can redeploy a previous version that you know works, or configure your environment to ignore health checks during deployment and redeploy the new version to force the deployment to complete.

The option bolded above worked for me!

Now I’m back to happily coding and solving problems in my application :).

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s