Bug 1653699
| Summary: | Openstack : Cloud provider supports LB although '[LoadBalancer]' section is missing in openstack.conf | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yossi Boaron <yboaron> |
| Component: | Cloud Compute | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chaoyang> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | aos-bugs, asegurap, jokerman, lxia, mmccomas, xxia |
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-30 15:19:31 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
Yossi Boaron
2018-11-27 12:48:14 UTC
Here is a link to upstream commit that fixes this issue: https://github.com/kubernetes/kubernetes/commit/a78fc5926d6091fcae9df2ccac3a5a3182832ce4 I sent this PR upstream to address this issue: https://github.com/openshift/origin/pull/21554 Hi Yossi, thanks for the PR and resolution of the issue. Jan It is passed on openshift v3.11.69 kubernetes v1.11.0+d4cacc0 [root@qe-chaoyang-master-etcd-nfs-1 ~]# oc logs master-controllers-qe-chaoyang-master-etcd-nfs-1 | grep LoadBalancer I0117 03:25:57.969058 1 openstack.go:575] openstack.LoadBalancer() called I0117 03:25:57.969093 1 openstack.go:578] LoadBalancer section is empty/not defined in cloud-config 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:0096 |