Bug 1984049 - Slow OVN Recovery on SNO
Summary: Slow OVN Recovery on SNO
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: ffernand
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks: 2008589
TreeView+ depends on / blocked
 
Reported: 2021-07-20 13:58 UTC by browsell
Modified: 2021-10-18 17:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2008589 (view as bug list)
Environment:
Last Closed: 2021-10-18 17:40:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1159 0 None None None 2021-08-26 13:29:46 UTC
Github openshift cluster-network-operator pull 1200 0 None open Bug 1984049 - Slow OVN Recovery on SNO 2021-09-21 18:50:06 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:40:43 UTC

Comment 1 Ben Bennett 2021-07-20 14:14:58 UTC
Tech note.  We need to change:
  https://github.com/openshift/cluster-network-operator/blob/master/bindata/network/ovn-kubernetes/ovnkube-master.yaml#L377

We need to templatize it so that when the number of masters == 1 we do not wait, otherwise we leave the behavior unchanged.

Longer-term we need to look at our delay policy and see if we can change the readiness so that we do not need to special case when there is one master.

Comment 9 errata-xmlrpc 2021-10-18 17:40:26 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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.

https://access.redhat.com/errata/RHSA-2021:3759


Note You need to log in before you can comment on or make changes to this bug.