Failed to update eb environment


#1

I’ve encountered this errors these days.
Uploading application zip file to s3 success, but updating elastic beanstalk always failed due to ‘No Application Version Named xxxxx’

Here’s my log.


Fetching changes started.
Fetching changes finished.
Pulling image buddy/aws-cli:latest

Creating new application version: app-245194-fbc064f0f9f7201e45efbb3628714ce9d2c8da3c
rm -f /buddy/app/app.zip
zip -r --symlinks /buddy/app/app.zip * .* -x …/* -x *.git/*
adding: app.json (deflated 45%)

adding: .gitignore (deflated 34%)

aws s3 cp app.zip s3://buddy-eb-ap-northeast-2-35712/app-245194/fbc064f0f9f7201e45efbb3628714ce9d2c8da3c/app.zip
Completed 256.0 KiB/12.9 MiB (177.3 KiB/s) with 1 file(s) remaining

Completed 12.9 MiB/12.9 MiB (2.5 MiB/s) with 1 file(s) remaining
upload: ./app.zip to s3://buddy-eb-ap-northeast-2-35712/app-245194/fbc064f0f9f7201e45efbb3628714ce9d2c8da3c/app.zip

An error occurred (InvalidParameterValue) when calling the CreateApplicationVersion operation: No Application named ‘? ?? Elastic Beanstalk ???’ found.

Updating environment…
aws elasticbeanstalk update-environment --application-name=“첫 번째 Elastic Beanstalk 애플리케이션” --environment-id=“e-cfpnddznqs” --version-label=“app-245194-fbc064f0f9f7201e45efbb3628714ce9d2c8da3c”

An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: No Application Version named ‘app-245194-fbc064f0f9f7201e45efbb3628714ce9d2c8da3c’ found.
Action failed: see logs above for details


strange thing is this project always works but stop working several days before.
where do I start to check?
thank you.


#2

Hi Daewook,
Please send the url to the failed execution on our intercom, we’ll have a look at this. Our initial guess are Korean characters in the application name.


#3

This is failed execution url below.
https://app.buddy.works/gamepletebuildbot/cardcraftserver/pipelines/pipeline/149412/execution/5b87aa4b63115e4885a77510

Strange thing is same setting, except different environment build has no problem. Even though it also says warning Korean application name.

Thank you! :slight_smile:


#4

We have identified the error and indeed confirm that there’s a problem with coding Korean characters. We will let you know when the fix goes live, stay tuned.


#5

Daewook,
We’ve fixed that. Could you confirm it’s working now?


#6

Yes, it’s working perfectly!
Thanks for your fast respond.
:slight_smile: