AWS Elastic Beanstalk - ERROR: No Application Version named 'v0_9_2-76-gf5a4' found

Question

I'm trying to deploy my code to AWS Beanstalk and get this error. I researched that it could be that the number of versions is more than 500, so I deleted a lot of versions. But, I still get this error.

eb deploy
ERROR: No Application Version named 'v0_9_2-76-gf5a4' found.

I also tried

git aws.push
Error: Failed to create the AWS Elastic Beanstalk application version

Edit: Trying with eb deploy --debug I now get:

Instance: i-2ad238d5 Module: AWSEBAutoScalingGroup ConfigSet: null Command failed on instance. Return code: 1 Output: Error occurred during build: Command hooks failed . Script /opt/elasticbeanstalk/hooks/appdeploy/pre/10_bundle_install.sh failed with returncode 18

ebcli.objects.exceptions.ServiceError: Update environment operation is complete, but with errors. For more information, see troubleshooting documentation.

eb deploy /opt/elasticbeanstalk/hooks/appdeploy/pre/10_bundle_install.sh failed with returncode 18 ERROR: [Instance: i-2ad238d5 Module: AWSEBAutoScalingGroup ConfigSet: null] Command failed on instance. Return code: 1 Output: Error occurred during build: Command hooks failed — user2974739, May 11 '15 at 18:08
vipul$ eb deploy --debug 2015-05-11 11:06:27,291 (DEBUG) eb : logging initialized for 'eb' using LoggingLogHandler 2015-05-11 11:06:27,291 (DEBUG) cement.ext.ext_plugin : plugin config dir /etc/eb/plugins.d does not exist. 2015-05-11 11:06:27,292 (DEBUG) cement.ext.ext_plugin : plugin config dir /Users/vipul/.eb/plugins.d does not exist. 2015-05-11 11:06:27,294 (DEBUG) eb : collecting arguments/commands for 2015-05-11 11:06:27,298 (DEBUG) eb : collecting arguments/commands — user2974739, May 11 '15 at 18:14
You'll have to add it as an edit to your question or put in pastebin or something because a comment is not sufficient for all the debug log. — Nick Humrich, May 11 '15 at 21:52
I just updated the question. Instance: i-2ad238d5 Module: AWSEBAutoScalingGroup ConfigSet: null Command failed on instance. Return code: 1 Output: Error occurred during build: Command hooks failed . Script /opt/elasticbeanstalk/hooks/appdeploy/pre/10_bundle_install.sh failed with returncode 18 INFO: New application version was deployed to running EC2 instances. ERROR: Update environment operation is complete, but with errors. For more information, see troubleshooting documentation. — user2974739, May 11 '15 at 23:02
This error usually happens because of dependencies or .ebextensions. Are you using .ebextensions? — Nick Humrich, May 12 '15 at 00:02
Elastic Beanstalk used to have issues with package names. I remember having issues with "-" in the names. I don't deploy manually anymore. You can try by removing dashes? — Rakesh Bollampally, May 12 '15 at 12:05

score 15 · Answer 1 · answered Jun 23 '16 at 08:46

15

Did you update the file .elasticbeanstalk/config.yml ? It may have a wrong setup.

Make a backup of .elasticbeanstalk/ folder and remove it
Execute eb create
Select the same region you deployed it before. You can check the region on .elasticbeanstalk/config.yml backup
A list with the environments will appear, select the right one
Deploy now
Remove the .elasticbeanstalk/config.yml backup

answered Jun 23 '16 at 08:46

albert

4,290
1
21
42

1

I had a different region and application name. Thanks! – Oscar Nevarez Aug 11 '16 at 22:37
In my case, I had to run eb -init to add SSH support, and the application_name in config.yml changed. – Matthew Pitts Mar 18 '19 at 17:52
1

For step 2 it should rather be "eb init", this command creates a new config.yml file – Greg Holst Mar 06 '20 at 09:53
@albert if it wasn't against stackoverflow rules I would make aa million temp accounts and up vote this aggressively. thank you! – alex_milhouse Feb 18 '23 at 18:55

score 8 · Answer 2 · edited Apr 30 '18 at 20:25

8

Check for the .elasticbeanstalk/config.yml file

environment: CORRECT_ENV_NAME
   global:
     application_name: CORRECT_APP_NAME

edited Apr 30 '18 at 20:25

Syscall

19,327
10
37
52

answered Apr 30 '18 at 20:21

Gal Bracha

19,004
11
72
86

score 4 · Answer 3 · answered Nov 03 '17 at 18:38

4

In my case, I was doing eb deploy X where X was an environment for a different project.

answered Nov 03 '17 at 18:38

jaynp

3,275
4
30
43

score 1 · Answer 4 · answered Sep 27 '18 at 14:36

1

When I had the error

InvalidParameterValueError: No Application Version named 'app-9f5c-180927_071528' found.

I fixed this by specifying the label I wanted to push up.

eb deploy XXX-env -l XXX.0.0.1

The -l flag is documented AWS EB Deploy Docs

answered Sep 27 '18 at 14:36

Brian Ludwig

11
1
2

Good call. Easy mistake to make. --version for an existing version, --label to create a version from that label. – Ted May 30 '19 at 10:29

score 0 · Answer 5 · answered May 25 '19 at 09:13

most likely, the deploy is trying an incorrect Elasticbeanstalk Application. it could be because you renamed the application in the AWS console.

so double check you're pointing to the correct elasticbeanstalk Environment and Application. it could be picking out default values from your .elasticbeanstalk/config.yml file.

AWS Elastic Beanstalk - ERROR: No Application Version named 'v0_9_2-76-gf5a4' found

5 Answers5