-
Notifications
You must be signed in to change notification settings - Fork 17
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
Previous application version is not decommissioned #8
Comments
Hello, |
Ok. Thanks. This is also the workaround I have applied. |
If you already have a fix/workaround could you please submit a pull request ? |
I mean I called a task to stop the service before the role. |
Issue fix now, actually symlink changes were not trigger service restart. it should be Ok now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an existing version of the application is runnning(e.g.: 1.0.0) and new version 1.0..1 is beeing deployed, I would expect the instanvce running the previous version to be stopped and a new instance with the new version to be started.
Actually, I can still see the previous version running after the playbook is run successfully.
The text was updated successfully, but these errors were encountered: