AWS EB Error: Incorrect application version found on all instances

Question

I am trying to use the EB CLI to deploy an application into an environment but I seem to be getting strange errors. Is there a way to empty out previous application versions so I can upload a fresh application?

The message I see after I execute eb deploy.

Update environment operation is complete, but with errors. For more information, see troubleshooting documentation.

I am currently getting this error:

Incorrect application version found on all instances. Expected version [app version]

The logs file also seems to be getting deleted for some reason.

score 33 · Answer 1 · edited Aug 09 '21 at 23:39

33

I solved this by doing an instance reboot. Redeploy worked well after reboot.

edited Aug 09 '21 at 23:39

Gerardo BLANCO

5,590
1
16
35

answered Aug 18 '19 at 16:44

Jeff Gu Kang

4,749
2
36
44

3

Thank you it did the trick! For those who dont see this pane, see instruction for enabling enhanced health monitoring – S.Daineko Aug 06 '20 at 19:14

score 15 · Answer 2 · answered May 09 '16 at 01:26

15

The operation completed but there were errors means that your deployment did not succeed. When an application update is unsuccessful eb will keep using the last good version. So if the last good version is 48 but this deployment is 55 and eb is expecting 54, then that "error" will be present... More of a warning than an error.

Something in your application is causing the application update to fail... Use the GUI to get the full logs which will reveal the error... Fix the error and when your deployment is successful your "Incorrect application version" error will resolve.

answered May 09 '16 at 01:26

hephalump

5,860
1
22
23

1

Ah thanks, the problem is that both 'eb logs' and the gui logs show nothing after the deployment failure. One of the events says, "deleting log fragments". Do you know why that is? – Sunwoo Yang May 09 '16 at 05:05
Can you ssh to the instance? – Rohit Banga May 10 '16 at 05:11
The error will not be at the end, it will be further up the logs... Even after the deployment fails, lots still happens, and is logged. 'Eb logs' only returns the last 100 lines, you need the full log files. – hephalump May 10 '16 at 19:53
Is this a rails application? – hephalump May 10 '16 at 19:54
4

Logs are not very helpful at finding what's wrong during deployment. – Val Berthe Mar 09 '22 at 16:30

score 5 · Answer 3 · answered Dec 01 '19 at 19:14

5

I found out that the issue was due to incompleteness of the permissions granted to the codepipeline/deployment service role.

You should grant UpdateApplicationversion permission to the associated elastic beanstalk resources for the role that you use to deploy your app.

answered Dec 01 '19 at 19:14

informeto

162
2
14

how can I add this permission please? – Mee Jan 28 '23 at 22:18

score 2 · Answer 4 · answered Oct 13 '22 at 13:37

2

Changing the application/package version in package.json and redeploying it worked for me.

answered Oct 13 '22 at 13:37

shiva prasad reddy puchala

31
3

score 1 · Answer 5 · edited Jun 17 '21 at 11:28

1

I faced the same problem and the cause was the command timeout

Default max deployment time -Command timeout- is 600 (10 minutes)

Go to Your Environment → Configuration → Deployment preferences → Command timeout

Increase the Deployment preferences for example 1800

or upgrade the instance type to work faster

edited Jun 17 '21 at 11:28

Dharman

30,962
25
85
135

answered Jun 17 '21 at 11:23

Majali

480
7
11

score 1 · Answer 6 · answered Mar 14 '23 at 21:28

I was getting this error in my EB application

Incorrect application version found on all instances. Expected version "Sample Application"

As @shiva prasad reddy puchala mentioned, changing the application version in the package.json solved this issue for me.

score 0 · Answer 7 · answered Nov 08 '21 at 14:03

0

Rebuilding the environment and deploying the new application version should solve the issue.

answered Nov 08 '21 at 14:03

palden

29
3

score 0 · Answer 8 · answered May 10 '22 at 17:03

0

Also faced this problem, and also the real problem seems to be a previous one, in my case I have CodeDeploy lacking permission on Cloud Watch, which made the deployment fail.

I can see both problems in the events section of Elastic Beanstalk.

answered May 10 '22 at 17:03

doper

33
7

AWS EB Error: Incorrect application version found on all instances

8 Answers8