Pybal considers the 30[12] TLS redirects to be failures. I've worked around the pragmatic immediate-term issue by avoiding the situation (ProxyFetch only on HTTPS, not HTTP services), but in the long term we should fix this so that we can healthcheck our public HTTP services fully, which will return 301s for most things going forward...
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Joe | T113151 pybal fails to detect dead servers under production lb IPs for port 80 | |||
Resolved | Joe | T102393 Make pybal accept 30[12] for ProxyFetch |
Event Timeline
Change 218285 had a related patch set uploaded (by BBlack):
Revert s/en/de/ for LVS monitoring; switch ProxyFetch to TLS
Switched this task up a bit. We'll merge the patch above to get past short term issues, and this is now about fixing it for good later.
Change 218285 merged by BBlack:
Revert s/en/de/ for LVS monitoring; switch ProxyFetch to TLS
Change 233054 had a related patch set uploaded (by Ori.livneh):
Make pybal accept 30[12] for ProxyFetch
Change 243139 had a related patch set uploaded (by Giuseppe Lavagetto):
Add support for http_status to ProxyFetch
Change 430393 had a related patch set uploaded (by Mark Bergsma; owner: Mark Bergsma):
[operations/debs/pybal@master] Handle HTTP status 302 and 303 as well as 301
Change 430393 merged by jenkins-bot:
[operations/debs/pybal@master] Handle HTTP status 302 and 303 as well as 301