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

Fix #7997: describe how to upgrade Salt Minion in a proper way #39952

Merged
merged 1 commit into from Mar 10, 2017
Merged

Fix #7997: describe how to upgrade Salt Minion in a proper way #39952

merged 1 commit into from Mar 10, 2017

Conversation

vutny
Copy link
Contributor

@vutny vutny commented Mar 10, 2017

What does this PR do?

Updates FAQ with Salt Minion upgrade techniques using modern Salt facilities and hacky workarounds for Debian.

What issues does this PR fix or reference?

Should resolve issue #7997

@cachedout cachedout merged commit 6350b07 into saltstack:2016.11 Mar 10, 2017
4 of 6 checks passed
@cachedout
Copy link
Contributor

cachedout commented Mar 10, 2017

Great! Thanks for taking this one on, @vutny

@vutny vutny deleted the doc-faq-minion-upgrade-restart branch Mar 13, 2017
@F30
Copy link
Contributor

F30 commented Oct 6, 2017

I experienced some issues deploying the new solution: The Master loses connection to the Minion upon restart, which makes it print a "Minion did not return. [No response]" error and probably also aborts the highstate run for that Minion. I fixed this by adding order: last, which is what I also had been using with the previous (nohup-based) solution.

Two additional notes:

  • Contrary to what the new heading suggests, this solution is not only helpful for restarts after upgrades, but for all restarts, e.g. also after changes to the Minion config.
  • A similar procedure also has to be deployed for restarting the Salt Master.

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

Successfully merging this pull request may close these issues.

None yet

3 participants