Bug 2059677

Summary: [osp][octavia lb] cannot create LoadBalancer type svcs
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Cloud ComputeAssignee: Martin André <m.andre>
Cloud Compute sub component: OpenStack Provider QA Contact: Jon Uriarte <juriarte>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: andcosta, cshepher, emacchi, gferrazs, juriarte, mabajodu, m.andre, mbooth, mdulko, mfedosin, mfojtik, nagrawal, pprinett, shiftstack-bugwatcher, stephenfin
Version: 4.8Keywords: Triaged
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: There's a race condition between OpenStack credentials secret creation and kube-controller-manager startup. Consequence: If it happens OpenStack cloud-provider will not get configured with OpenStack credentials, effectively breaking support for creating Octavia load balancers for LoadBalancer services. Fix: Retry fetching the OpenStack credentials secret until it succeeds during the kube-controller-manager started. Result: The OpenStack cloud-provider is now consistently initialized upon kube-controller-manager startup.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-24 01:48:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2054669    
Bug Blocks:    

Comment 1 ShiftStack Bugwatcher 2022-03-02 07:03:35 UTC
Removing the Triaged keyword because:
* the QE automation assessment (flag qe_test_coverage) is missing

Comment 5 Jon Uriarte 2022-03-18 09:29:29 UTC
LB tests in downstream CI are passing with OCP 4.6.56. LB type IngressController
tests may fail with OpenshiftSDN and OVNKubernetes due to the bug 2018481.

Comment 8 Scott Dodson 2022-08-24 01:48:06 UTC
This was addressed in 4.6.56 however the errata automation failed to close this bug as it should have.