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

Bug 1771623

Summary:	Requesting bump to CRI-O to include PodIP networking fix
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	RHCOS	Assignee:	Micah Abbott <miabbott>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Nguyen <mnguyen>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bbreard, dustymabe, imcleod, jligon, nstielau
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:	2019-11-13 18:57:39 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 Stephen Benjamin 2019-11-12 17:09:41 UTC

Description of problem:

A bug was introduced into CRI-O that sets the PodIP incorrectly, even if a pod is using host networking. This overrides Kubernetes default behavior of assinging the node IP. This is breaking the baremetal IPI platform[1]

The cherry-pick PR that pulls this into CRI-O 1.16 is located at https://github.com/cri-o/cri-o/pull/2944, after this is merged, we'd like to request the version in RHCOS be bumped to include that as soon as possible.

[1] https://github.com/openshift/installer/issues/2646#issuecomment-552983562

Comment 1 Stephen Benjamin 2019-11-12 17:10:55 UTC

The cherry-pick PR is actually https://github.com/cri-o/cri-o/pull/2949.

Comment 3 Stephen Benjamin 2019-11-13 18:57:39 UTC

This is now in 43.81.201911131545.0