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
Do not fallback to 127.0.0.1 for un-resolvable masters in failover mode #57699
Conversation
@sergeyfd could you please write a test for your change? |
Yes, I'll try. For some reason "setup.py test" fails in my setup with import error for saltfactories. |
@sergeyfd have you tried
You also can specify the test you want to run with colons:
|
That works, thanks! Will add a couple of unit tests later this week. |
@sergeyfd thank you! Glad to help! Ping me anytime here or in community Slack |
@DmitryKuzmenko , done. Please take a look. Should have done it from the beginning, the patch was slightly incorrect. |
tests/unit/test_minion.py
Outdated
self.assertEqual(opts["master"], "master2") | ||
return MockPubChannel() | ||
|
||
io_loop = salt.ext.tornado.ioloop.IOLoop() |
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.
There is a tornado testing package that makes things a way easier for testing async code.
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.
I am not sure it deserves it because it doesn't test any async functionality. io_loop here isn't needed here at all, so I removed it.
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.
@DmitryKuzmenko Are we Ok now?
@sergeyfd thank you for your work! Could you please take a look at the mentioned tornado testing package and update the tests correspondingly? The package is already used in some tests you can just grep |
I'm good now, thank you! |
@sergeyfd it looks timeout failures are related:
|
Sorry I can't say anything useful by a quick look. I'll return to this later to analyze the failures. |
rerun windows |
re-run windows2016 |
re-run windows2019 |
@krionbsd I don't think re-run will help. It constantly times out on these new unit tests in Windows. Don't know why. |
We are looking into the Windows tests as they are a problem more globally. |
Congratulations on your first PR being merged! 🎉 |
What does this PR do?
Do not fall back to 127.0.0.1 in DNS resolution for master nodes in master_type is `failover'
What issues does this PR fix or reference?
Fixes: #57660
Merge requirements satisfied?
Commits signed with GPG?
No