Bug 1844091

Summary: Find_loadbalancer method should also use provider information
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Luis Tomas Bolivar <ltomasbo>
Networking sub component: kuryr QA Contact: GenadiC <gcheresh>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: medium CC: rlobillo
Version: 4.5Keywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-23 00:57:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1843817    
Bug Blocks:    

Description OpenShift BugZilla Robot 2020-06-04 15:31:07 UTC 
+++ This bug was initially created as a clone of Bug #1843817 +++

+++ This bug was initially created as a clone of Bug #1842466 +++

Since OpenShift 4.4, kuryr support both amphora and ovn octavia loadbalancer drivers. Kuryr should differentiate existing loadbalancer depending on its provider too
Comment 3 rlobillo 2020-06-15 16:18:12 UTC 
As the required conditions to match this scenario requires to perform amphora to ovn-octavia upgrade and this is still not supported, we agreed to verify by code on OCP 4.4.0-0.nightly-2020-06-14-142924 on OSP13(2020-06-09.2).

Tests run as expected while code is confirmed to be present on the running kuryr-controller POD:

$ oc rsh -n openshift-kuryr kuryr-controller-78494d6fdd-s58g6 sed -n -e 623p -e 624p /usr/lib/python3.6/site-packages/kuryr_kubernetes/controller/drivers/lbaasv2.py
            vip_subnet_id=loadbalancer.subnet_id,
            provider=loadbalancer.provider)
Comment 5 errata-xmlrpc 2020-06-23 00:57:50 UTC 
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-2020:2580