Bug 2018129

Summary: Kuryr controller crash looping on self._get_vip_port(loadbalancer).id 'NoneType' object has no attribute 'id'
Product: OpenShift Container Platform Reporter: Michał Dulko <mdulko>
Component: NetworkingAssignee: Michał Dulko <mdulko>
Networking sub component: kuryr QA Contact: rlobillo
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: akaris, dhill, juriarte, mdemaced, mdulko, rcernin
Version: 4.6Keywords: Triaged
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2014538 Environment:
Last Closed: 2021-12-06 11:22:25 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: 2014538    
Bug Blocks:    

Comment 5 rlobillo 2021-12-01 07:30:52 UTC
Verified in 4.9.0-0.nightly-2021-11-29-233413 on top of OSP16.1 (RHOS-16.1-RHEL-8-20210903.n.0) with OVN-Octavia.

The LB creation logic has changed from: 

1. Create LB
2. Populate result with that LB
3. If there was a failure during "Create LB"
4. Find LB
5. Update KLB CRD.


1. Check if LB exists, and if it does, re-use the same LB.
2. If it doesn't exist, then create new LB
3. Populate result with that LB
4. Update KLB CRD

This new logic is working as expected, as confirmed by installation and running kuryr-tempest-plugin tests (Logs attached).

It is agreed with the BZ assignee that this is enough for validating this fix, as the systematic reproduction requires code modification.

Comment 9 errata-xmlrpc 2021-12-06 11:22:25 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 (OpenShift Container Platform 4.9.10 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.