You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?).
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
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.
The text was updated successfully, but these errors were encountered: