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

Previous application version is not decommissioned #8

Closed
lucimihai opened this issue Mar 27, 2019 · 5 comments
Closed

Previous application version is not decommissioned #8

lucimihai opened this issue Mar 27, 2019 · 5 comments

Comments

@lucimihai
Copy link

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.

@orachide
Copy link
Owner

Hello,
I’ll make a fix for that. I’ll only stop the previous version but not uninstall it.

@lucimihai
Copy link
Author

Ok. Thanks.

This is also the workaround I have applied.

@orachide
Copy link
Owner

If you already have a fix/workaround could you please submit a pull request ?

@lucimihai
Copy link
Author

I mean I called a task to stop the service before the role.

@orachide
Copy link
Owner

orachide commented Apr 6, 2019

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants