Skip to content
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

Roll back fix for 1405440 #13331

Merged
merged 1 commit into from
Mar 11, 2017
Merged

Conversation

pecameron
Copy link
Contributor

@pecameron pecameron commented Mar 9, 2017

The fix to use a TCP connection check to check whether the HAProxy
process is alive or not doesn't work without a iptables rule for port
1936. The original test using HTTPGet works because HTTPGet supports
a Host field that can be set with "localhost" when host networking is
used. The TCPSocketAction does not support a Host field.

Rolling back the fix until a new fix is developed.

bug 1430729

Signed-off-by: Phil Cameron pcameron@redhat.com

@pecameron
Copy link
Contributor Author

@knobunc @danwinship @dcbw Rolled back the fix for 1405440. PTAL

@danwinship
Copy link
Contributor

standard git way to do this would be "git revert 5b708a5", which then makes it completely clear that this is just reverting an earlier commit

This reverts commit 5b708a5.
@pecameron
Copy link
Contributor Author

@danwinship Did I get this right? PTAL

@danwinship
Copy link
Contributor

yeah, looks right

@pecameron
Copy link
Contributor Author

@danwinship @dcbw @eparis Is this ready to merge? If so will one of you merge it?

@louyihua
Copy link
Contributor

louyihua commented Mar 10, 2017

Maybe the health check can be performed on port 80, which should be guarenteed to be permitted by iptables to support router's function. (#13345)
I'll also try to submit a PR on kubernetes so that the TCPSocketAction can have an option to use loopback address for probe. If this is implemented one day, we can switch to use the loopback TCPSocketAction on stats port again.
So @danwinship @dcbw @eparis what's your opinion?

@imcsk8
Copy link
Contributor

imcsk8 commented Mar 10, 2017

It sounds like a good option

@pecameron
Copy link
Contributor Author

@louyihua The HTTPGet handler also had problems (see comment pkg/cmd/admin/router/router.go line 423) so adding Host to the TCPSocketAction may be all that is needed.

@louyihua
Copy link
Contributor

@pecameron
Yes, this is the best way to solve this problem, and I've prepared a preliminary PR submitted to kubernetes (kubernetes/kubernetes#42902) .

@eparis
Copy link
Member

eparis commented Mar 10, 2017

[merge] to fix broken, we can try again once everyone agrees on the next path.

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 0d8009f

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test UNSTABLE (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/123/) (Base Commit: 93525f2)

@eparis
Copy link
Member

eparis commented Mar 11, 2017

guess it was a flake [merge] because last time it was #11114

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 0d8009f

@openshift-bot
Copy link
Contributor

openshift-bot commented Mar 11, 2017

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/54/) (Base Commit: 31e9bd0) (Image: devenv-rhel7_6067)

@openshift-bot openshift-bot merged commit 54af0f3 into openshift:master Mar 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants