Bug 1550007
Summary: | Router cannot be running when enable 'ROUTER_BIND_PORTS_AFTER_SYNC' for system container install env | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
Component: | Networking | Assignee: | Jacob Tanenbaum <jtanenba> |
Networking sub component: | router | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | aos-bugs, bbennett, hongli, zzhao |
Version: | 3.9.0 | ||
Target Milestone: | --- | ||
Target Release: | 3.11.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
The liveness and readiness probes where the same checks
Consequence:
The router pod could not differentiate between a pod that was alive and one that was ready
Fix:
Create two probes one for readiness and one for liveness
Result:
a router pod can be alive but not yet ready
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-11 07:19:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
zhaozhanqi
2018-02-28 09:45:49 UTC
Can you still reproduce? I saw the behaviour but after deleting the first attempted pod deployed the dc was able to spawn a valid pod, does that happen on your setup? yes, this issue still can be reproduced in system container installed env. the router cannot be running when enable 'ROUTER_BIND_PORTS_AFTER_SYNC' Even if I delete the first attempted pod. Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/978d2bc3de43445e4809193016ee7f658ca1348a Differentiate liveness and readiness probes for router Add a backend to the router controller "/livez" that always returns true. This differentiates the liveness and readiness probes so that a router can be alive and not ready. Bug 1550007 verified in openshift v3.11.0-0.21.0 and issue has been fixed. Operation System: Red Hat Enterprise Linux Atomic Host release 7.5 Cluster Install Method: system container kernel: Linux qe-master-etcd-1 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652 |