Bug 1641647
| Summary: | kuryr-controller cannot access OpenShift API LB members with OVN if running on master nodes | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luis Tomas Bolivar <ltomasbo> |
| Component: | Installer | Assignee: | Luis Tomas Bolivar <ltomasbo> |
| Installer sub component: | openshift-ansible | QA Contact: | Jon Uriarte <juriarte> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | aos-bugs, gpei, jokerman, juriarte, mmccomas |
| Version: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
When using OVN, LoadBalancer members cannot access themselves through the LoadBalancer VIP.
Consequence:
If kuryr-controller pod (which uses host-networking) is running on a master node (where the OpenShift API is running), then the kuryr-controller cannot access the OpenShift API
Fix:
Forces kuryr-controller to be on infra nodes
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-24 08:08:08 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
Luis Tomas Bolivar
2018-10-22 12:38:46 UTC
Verified on openshift-ansible-3.11.141 on top of OSP 13 2019-06-25.1 puddle. Kuryr-controller pod runs on an infra node: [openshift@master-0 ~]$ oc get pods -n kuryr -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE kuryr-cni-ds-6h8q2 2/2 Running 1 2h 192.168.99.16 master-0.openshift.example.com <none> kuryr-cni-ds-gnr79 2/2 Running 1 2h 192.168.99.7 infra-node-2.openshift.example.com <none> kuryr-cni-ds-j9pcr 2/2 Running 0 2h 192.168.99.14 app-node-1.openshift.example.com <none> kuryr-cni-ds-n4klv 2/2 Running 0 2h 192.168.99.6 app-node-0.openshift.example.com <none> kuryr-cni-ds-sks7m 2/2 Running 1 2h 192.168.99.9 master-1.openshift.example.com <none> kuryr-cni-ds-tcvk8 2/2 Running 0 2h 192.168.99.30 infra-node-0.openshift.example.com <none> kuryr-cni-ds-x6f66 2/2 Running 2 2h 192.168.99.23 master-2.openshift.example.com <none> kuryr-cni-ds-zg5j2 2/2 Running 0 2h 192.168.99.12 infra-node-1.openshift.example.com <none> kuryr-controller-7cf75d55c9-fnq9q 1/1 Running 3 2h 192.168.99.7 infra-node-2.openshift.example.com <none> 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-2019:2816 |