Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1776894

Summary:	Race between pools recovery and previous request_vifs
Product:	OpenShift Container Platform	Reporter:	Luis Tomas Bolivar <ltomasbo>
Component:	Networking	Assignee:	Luis Tomas Bolivar <ltomasbo>
Networking sub component:	kuryr	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	juriarte
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1776896 1776897 (view as bug list)		Environment:
Last Closed:	2020-05-13 21:53:17 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:
Bug Depends On:
Bug Blocks:	1776896, 1776897

Description Luis Tomas Bolivar 2019-11-26 14:29:24 UTC

When kuryr-controller gets restarted, and before the pools are recovered, there is some pools repopulation events triggered due to handling events previous to the kuryr-controller restart. This leads to unneeded repopulation actions as well as delayed pools recovery

Comment 2 Jon Uriarte 2020-02-20 14:51:59 UTC

Verified in 4.4.0-0.nightly-2020-02-17-131733 build on top of OSP 13 2020-01-15.3 puddle.

The OCP installer finishes successfully:

 $ oc get clusterversion
 NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
 version   4.4.0-0.nightly-2020-02-17-131733   True        False         16h     Cluster version is 4.4.0-0.nightly-2020-02-17-131733

While running kubernetes/conformance test from origin the release-4.4 kuryr-controller pod showed next message:
"Kuryr-controller not yet ready to populate pools" and raised kuryr_kubernetes.exceptions.ResourceNotReady exception.

Comment 4 errata-xmlrpc 2020-05-13 21:53:17 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:0581