Bug 2005181

Summary:	[RHOCP 4.6.z][Backport request] failed to configure pod interface: error while waiting on flows for pod: timed out waiting for OVS flows
Product:	OpenShift Container Platform	Reporter:	Vincent Lours <vlours>
Component:	Networking	Assignee:	Ben Pickard <bpickard>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED EOL	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	anbhat, bbennett, bpickard, mcurry, vchalise, vpickard
Version:	4.6
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-26 23:19:53 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:

Description Vincent Lours 2021-09-17 03:32:58 UTC

Description of problem:
Following on the Bugzilla 1952819, Some customers are querying to get the fix backported to the EUS version 4.6.z
This Bug has been rated with a High severity, and according to the Maintenance support description, it may be eligible to be backported to the version 4.6 and 4.7

"During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) may be released as they become available. Other Bug Fix (and Enhancement (RHEA) Advisories may be released at Red Hat’s discretion, but should not be expected."


Version-Release number of selected component (if applicable):
4.6.42

Actual results:
Even if a KCS has been created for this bug, some customers are wondering if the fix will be backported to 4.6.z

Expected results:
have the fix in 4.6.z

Additional info:

Comment 4 Vibhuti Chalise 2021-09-23 01:06:45 UTC

@anbhat
CU is on OCP 4.6 EUS and their plan is to upgrade to next EUS which could likely be 4.10. 
Thus, they look forward to get this fix backported to 4.6.

Comment 8 Vincent Lours 2021-10-11 02:48:46 UTC

Hi Aniket, Ben

From the last information you shared, the fix is included in RHOCP 4.6.42

From the Release Notes (https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html#ocp-4-6-42), 
I was able to find the Errata RHBA-2021:3008 (https://access.redhat.com/errata/RHBA-2021:3008)
and then the Bugzilla 1985347 (https://bugzilla.redhat.com/show_bug.cgi?id=1985347).

But I'm wondering why the customer has faced the issue when updating to 4.6.42!

Does the fix prevent future issues, after updating to 4.6.42?
Or should have the fix avoid the issue in 4.6.42?

In the first case, we can say that the fix has already been backported in 4.6.42 and this BZ can be closed.

In another hand, if the fix was supposed to avoid this issue in 4.6.42, something is not working as expected.
And we may need to work on this again.

Cheers,

Comment 10 Vibhuti Chalise 2021-10-21 00:36:07 UTC

Hi Aniket, Ben,

Customer updated from 4.6.42 to 4.6.45 without issues. This BZ can be closed.
Thank you for your assistance. 

Vibhuti