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
{{ message }}
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
@aneeshusa, this seems like the best way of getting ahold of you at the moment. I've tried just removing the old key and restarting Salt, but that doesn't cause the minion to show up in the master's unaccepted keys list. Will we have to generate keys on the master and transfer them to the minion as suggested in https://docs.saltstack.com/en/2017.7/topics/tutorials/preseed_key.html?
If you don't have time to sort this out, I can continue through trial and error, but I suspect you may already know the best practices.
The text was updated successfully, but these errors were encountered:
Changing the ID should be sufficient; IIRC Salt will generate a new key once it sees a new minion id.
I don't remember how our install process sets the minion id, but there are two places to look:
It can be explicitly set in /etc/salt/minion (or an included file); update or add the new minion id here
That plus a minion restart should be sufficient, let me know if it's not working. Emailing me directly is another good way to get a hold of me. (I filter GH emails into a separate folder which I check occasionally as well.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@aneeshusa, this seems like the best way of getting ahold of you at the moment. I've tried just removing the old key and restarting Salt, but that doesn't cause the minion to show up in the master's unaccepted keys list. Will we have to generate keys on the master and transfer them to the minion as suggested in https://docs.saltstack.com/en/2017.7/topics/tutorials/preseed_key.html?
If you don't have time to sort this out, I can continue through trial and error, but I suspect you may already know the best practices.
The text was updated successfully, but these errors were encountered: