Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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.

like image 465
user2974739 Avatar asked May 11 '15 04:05

user2974739


People also ask

How many application version does Elastic Beanstalk allow you to store?

Elastic Beanstalk applies an application's lifecycle policy each time you create a new application version, and deletes up to 100 versions each time the lifecycle policy is applied.

What is Elasticbeanstalk config Yml?

Elastic Beanstalk supports two methods of saving configuration option settings. Configuration files in YAML or JSON format can be included in your application's source code in a directory named . ebextensions and deployed as part of your application source bundle. You create and manage configuration files locally.


2 Answers

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

  1. Make a backup of .elasticbeanstalk/ folder and remove it
  2. Execute eb create
  3. Select the same region you deployed it before. You can check the region on .elasticbeanstalk/config.yml backup
  4. A list with the environments will appear, select the right one
  5. Deploy now
  6. Remove the .elasticbeanstalk/config.yml backup
like image 170
albert Avatar answered Oct 12 '22 03:10

albert


Check for the .elasticbeanstalk/config.yml file

environment: CORRECT_ENV_NAME
   global:
     application_name: CORRECT_APP_NAME
like image 42
Gal Bracha Avatar answered Oct 12 '22 04:10

Gal Bracha