-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
bugfix for auth_safemode #46089
bugfix for auth_safemode #46089
Conversation
salt/minion.py
Outdated
@@ -2624,7 +2624,7 @@ def tune_in(self, start=True): | |||
def ping_master(): | |||
try: | |||
def ping_timeout_handler(*_): | |||
if not self.opts.get('auth_safemode', True): | |||
if self.opts.get('auth_safemode', True): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this was implemented incorrectly, but we should not have it switch to True, if it is not specified, it should be False
in the .get() as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rongzeng54 Did you see the feedback here?
re-run ubuntu |
re-run py3 |
What does this PR do?
bugfix for auth_safemode as the docs(https://docs.saltstack.com/en/develop/ref/configuration/minion.html) said:
`AUTH_SAFEMODE
New in version 2014.7.0.
Default: False
If authentication fails due to SaltReqTimeoutError during a ping_interval, this setting, when set to True, will cause a sub-minion process to restart.`
What issues does this PR fix or reference?
No
Tests written?
No
Commits signed with GPG?
No