Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

AWS Bean Stalk deployment failure

Edited

Hi All,

I am trying to do setup a CD pipeline using bitbucket pipelines and I am running into this issue of conflicting version error while trying to deploy.

The error message to be specific is this:

✖ Deployment failed. Environment "<current-env>" is running a different version "<current-running-version>".

 

I am using the built-in pipe to enable this: 

https://confluence.atlassian.com/bitbucket/deploy-to-aws-with-elastic-beanstalk-976772710.html

this has me stumped shouldn't the new deployment be a different version so why beanstalk complaining about this?

Any help is appreciated.

2 answers

I had a similar issue. In my case I had i error in the Nginx config file. I override the default config file but the path was wrong.

The configuration file should have the path ".platform/nginx/nginx.conf"

Beanstalk performs some king of staging within the instance before deploying the code. If there is any error. It won't deploy and you will see the error

 ✖ Deployment failed. Environment "<current-env>" is running a different version "<current-running-version>".

I was able to figure this up by analyzing the log  eb-engine.log. It may be hard to see the log directly in beanstalk so I suggest enabling pushing the log to cloud watch.

 

Hope this can help you

@Varenya firstly the pipe is deploying to new version that is different from current version in environment.

https://bitbucket.org/atlassian/aws-elasticbeanstalk-deploy/src/0545b1d8703a8ebe471cc3bf772cd56796f0e91f/pipe/pipe.sh#lines-120

Then after this environment is green the pipe is checking that it is exactly deployed with the version VERSION_LABEL mentioned above https://bitbucket.org/atlassian/aws-elasticbeanstalk-deploy/src/0545b1d8703a8ebe471cc3bf772cd56796f0e91f/pipe/pipe.sh#lines-141

And if they are not equal, this would mean that the current deployment is wrong because versions are not equal. So check the version deployed when you see your environment application was created and environment updated to that version https://bitbucket.org/atlassian/aws-elasticbeanstalk-deploy/src/0545b1d8703a8ebe471cc3bf772cd56796f0e91f/pipe/pipe.sh#lines-107

 

It may give you and us some more details about the failing, because it would be strange that environment is green but is running on different version from that the pipe just deployed

Looking forward to seeing your feedback

@Varenya to have quicker answer related to bitbucket pipelines pipes, add to your question tags `pipes` (necessary) and `bitbucket-pipelines`. Otherwise your question will appear in common queue and we might lose it

Cheers, Galyna

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

405 views 13 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you