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

Restart the minion anytime we need it #246

Open
vkurup opened this issue Feb 24, 2016 · 2 comments
Open

Restart the minion anytime we need it #246

vkurup opened this issue Feb 24, 2016 · 2 comments

Comments

@vkurup
Copy link
Contributor

vkurup commented Feb 24, 2016

On edutrac today, deploys failed without much feedback. It turned out that the salt-minion had died. Restarting the minion allowed the deploy to succeed. I have definitely seen this on other projects, and we have solved it in some projects by restarting the salt-minion as the first step of any deploy.

Given how confusing this failure is (since there's no feedback), I propose to restart the salt-minion during every deploy, but would also be interested in other suggestions.

@mlavin
Copy link
Contributor

mlavin commented Feb 24, 2016

Agree this is a problem but this could get messy for larger deploys. Restarting the minion means the fabfile knows where all of the minions are because you can't restart the minion via the salt master (can you?).

@vkurup
Copy link
Contributor Author

vkurup commented Feb 25, 2016

Hmm... good point. I just spent way too much time looking at saltstack/salt#7997 and saltstack/salt#5721, so I see that a general solution for a multi-server setup might be tricky

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