Bug 2104950

Summary:	Reintroduce kube1.24 for SDN
Product:	OpenShift Container Platform	Reporter:	Ken Zhang <kenzhang>
Component:	Networking	Assignee:	Dan Winship <danw>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	high
Priority:	high	CC:	rravaiol, trozet, wking
Version:	4.11
Target Milestone:	---
Target Release:	4.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2104953 (view as bug list)		Environment:
Last Closed:	2022-11-01 19:10:28 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:	2104953
Bug Blocks:

Description Ken Zhang 2022-07-07 14:48:40 UTC

Description of problem:
With the regression described in this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2101622, SDN's kube1.24 bump has been reverted. But it is critical to find the root cause of the disruption source and reintroduce kube1.24 back.

Please do run "/payload ci 4.11 blocking" on the PR when rebase is brought back!

Comment 2 Dan Winship 2022-07-21 12:37:58 UTC

It is not clear that we will actually do this... doing a kube y-stream rebase in a z-stream release is kinda sketchy...