Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different versions of application in same environment after update #97

Open
Epimetheus89 opened this issue Jan 4, 2017 · 0 comments
Open

Comments

@Epimetheus89
Copy link

Epimetheus89 commented Jan 4, 2017

We are using eb_deployer with blue-green deployment and the following settings:

environments:
  prod:
    inactive_settings:
      - namespace: aws:autoscaling:asg
        option_name: "MinSize"
        value: "1"
      - namespace: aws:autoscaling:asg
        option_name: "MaxSize"
        value: "1"

and having MinSize and MaxSize equal 2 in active_settings as default.

Now if we simply deploy a new version via eb_deploy -e prod, the environment is updated as follows:

  1. inactive environment is scaled up from 1 to 2 instances (seeing one instance added in elastic beanstalk log)
  2. new code version is deployed

Ending up in this state:

  • Old instance: new code version
  • New instance: old code version

So it seems that the newly added instance does not get the update of the new code.

Is this a bug in eb_deployer or in aws api? Can someone reproduce it?

Some more information:

  • Enhanced Elastic Beanstalk health states that both instances have the same version, so you have to look at the machines to verify versions.
  • AWS support asked if there is an application version specified while deploying the new configuration (upscaling)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant