Editing Troubleshooting Deploying a Django Application With Elastic Beanstalk (section)

== Package version not available on `eb deploy` ==

'''Use case'''

# Run `eb deploy`.
# Batch does not complete.
# Quits with error to the effect that a package version defined in `requirements.txt` is not available, e.g.:
<syntaxhighlight lang="text">
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: requests<2.7,>=2.6.1
</syntaxhighlght>

'''Cause '''

`awsebcli` package needs to be upgraded. (Not sure how this is getting set back to an earlier version.)

'''Fix'''

Upgrade `awsebcli` with `pip install --upgrade awsebcli`

== YAML formatting errors on `eb create` ==

'''Use case''' 

This is related to the previous troubleshooting case. 

Run `eb create` and receive error 

<syntaxhighlight lang="text">
ERROR: The configuration file .ebextensions/02-northrose.config in application version app-dd48-160209_151318 contains invalid YAML or JSON. YAML exception: while scanning for the next token
found character 	'\t' that cannot start any token
 in "<reader>", line 2, column 1:
    	"aws:elasticbeanstalk:applicati ... 
    ^
, JSON exception: Unexpected character (o) at position 0.. Update the configuration file.
</syntaxhighlight>

'''Cause'''

Not 100% certain about the cause. It's either that changes to the `.config` file needed to be checked in in order to be deployed to the EC2 instance. Or that I had tried recently to launch an environment with the same name, and so the config file in question was still seen in its old state in the previous environment.

'''Fix'''

1) Fixed the YAML formatting in the file. Committed the changes, and merged them into the `master` branch.

2) Took some time making the fixes, which possibly gave the AWS Management Console enough time to clear out the previous aborted Elastic Beanstalk environments that shared the environment name.