Bug 2059677 - [osp][octavia lb] cannot create LoadBalancer type svcs
Summary: [osp][octavia lb] cannot create LoadBalancer type svcs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Martin André
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On: 2054669
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-01 17:30 UTC by OpenShift BugZilla Robot
Modified: 2022-08-24 01:48 UTC (History)
15 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-08-24 01:48:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 1198 0 None open [release-4.6] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf 2022-03-08 15:41:16 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.