Bug 1391837
| Summary: | incorrect lbversion check | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jan Provaznik <jprovazn> |
| Component: | Node | Assignee: | Seth Jennings <sjenning> |
| Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.0 | CC: | agoldste, aos-bugs, ghuang, jeder, jialiu, jokerman, jprovazn, mmccomas, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | aos-scalability-34 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
This bug fixes an issue on the OpenShift master when using the Openstack cloud provider. The LBaaS version check was done improperly leading to failures when using v2 of the LBaaS plugin. This fix corrects the check so that v2 is detected properly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:49:42 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
Jan Provaznik
2016-11-04 08:14:39 UTC
Worth noting the severity of this bug (i.e. it is fatal to the master) is mitigated by https://bugzilla.redhat.com/show_bug.cgi?id=1389205 Kube PR: https://github.com/kubernetes/kubernetes/pull/36249 Origin cherry pick PR: https://github.com/openshift/origin/pull/11789 Thanks for the quick fix Seth. BZ 1389205 is fatal for openstack envs where LBaaS is not available, in opposite this BZ is fatal for openstack envs where LBaaS v2 is available (supposing LBaaSv1 is deprecated, it would be majority), so AIUI fixing of 1389205 has no impact on severity of this bug. The call chain is MasterConfig RunServiceLoadBalancerController() ServiceController.New() ServiceController.init() cloudprovider.LoadBalancer() PR: https://github.com/openshift/origin/pull/11648/files Before the PR, if LoadBalancer() returned an error, it would result in a glog.Fatalf() in RunServiceLoadBalancerController(). After the PR, LoadBalancer() failure only does glog.Errorf() and prevents the start of the service controller, rather than killing the whole master. In other words it prevents this from being fatal: F1104 03:46:11.118558 92992 master.go:453] Unable to start service controller: the cloud provider does not support external load balancers. Ah, right, thanks. This has been merged into ose and is in OSE v3.4.0.24 or newer. @Jan, because QE do not have a openstack with LbaasV2 installed, we only have a OSP9 + LbaasV1, could you help verify this bug? Unfortunately I don't have an env with LBaasV2 at the moment too, we hit this when we manually enabled LBaaSv2 in the scale lab as a workaround for BZ 1389205 but disabled it again when BZ 1389205 was fixed. Is it possible to enable LBaasV2 on OSP9, if yes, could you tell me how to enable it? Supposing neutron-lbaas packages are available in OSP9 then yes (I think these are avail, but I can not confirm - I used OSP10). You can follow http://docs.openstack.org/mitaka/networking-guide/config-lbaas.html Testing in OSP9 which enables LBaaSv2.(cloudprovider is enabled in OpenShift) Verified with openshift v3.4.0.26 1.Reproduced with openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 Master can't start due to "getsockopt: connection refused". Start the atomic-openshift-master service manually, there's a similar error threw out like Jan's report: #/usr/bin/openshift start master --config=/etc/origin/master/master-config.yaml --loglevel=10 I1116 02:56:19.056420 3650 openstack.go:410] Using LBaaS extension v2 I1116 02:56:19.056440 3650 openstack.go:413] Claiming to support LoadBalancer W1116 02:56:19.056448 3650 openstack.go:420] Config error: unrecognised lb-version "v2" F1116 02:56:19.056457 3650 master.go:453] Unable to start service controller: the cloud provider does not support external load balancers. 2. Trigger a fresh installation with openshift v3.4.0.26+f7e109e kubernetes v1.4.0+776c994 Installation succeed, Master and Node services both are working well, S2I build succeed. Move to verified. 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-2017:0066 |