-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
reverseproxy: fix breakage in handling SRV lookup introduced by d55d50b #3756
Conversation
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.
Awesome, thanks for making time to help fix this!
FWIW, I think it looks fine; I'd have probably done something similar. Since health checks don't make sense on srv upstreams, should we take this opportunity to make it an error?
Awesome @mohammed90, I validated the build and it fixes the issue! |
Thank you so much. What is the release process? I really want to upgrade because of Prometheus metrics. |
@mholt is it possible to have this into a 2.2.1 release whenever its merged? |
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.
This fix LGTM! Are we comfortable merging it then? Will wait for the do not merge
and in progress
tags to be removed.
Just want to add a few validations for incompatible config and few integration tests. I should be able to shoot them later tonight. |
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.
Tests look great! Willing to merge this, my only nit is with a comment. Thanks!
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.
Yep, that'll work! As usual, thank you sooo much!
d1de52b
to
46ea82e
Compare
CI is failing apparently because Microsoft is having a major outage right now, so GitHub is naturally affected... |
Okay that's pretty stupid, it looks like it didn't dismiss the failing jobs after rerunning them all... 🤔 I think if you just force push again @mohammed90 it should be okay (force re-run CI) |
46ea82e
to
9bd1880
Compare
Co-authored-by: Francis Lavoie <[email protected]>
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.
Thanks for all the helpful fixes @mohammed90 😁
* reverse_proxy: ensure upstream address has port range of only 1 * reverse_proxy: don't log the error if upstream range size is more than 1
* reverseproxy: Fix dial placeholders, SRV, active health checks Supercedes #3776 Partially reverts or updates #3756, #3693, and #3695 * reverseproxy: add integration tests Co-authored-by: Mohammed Al Sahaf <[email protected]>
This is the naive fix. I still need to test it some more and figure whether this fix is the best.
@waiyip-aquabyte and @danlsgiga, is it possible to test using the CI artifacts? You can find them here.
Fixes #3753