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
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.
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.