Bug 2017881 - multus: add handling of pod UIDs passed from runtime
Summary: multus: add handling of pod UIDs passed from runtime
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On: 2017882
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-27 15:51 UTC by Douglas Smith
Modified: 2021-12-13 12:06 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2017882 (view as bug list)
Environment:
Last Closed: 2021-12-13 12:06:24 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift multus-cni pull 111 0 None open Bug 2017881: add handling of pod UIDs passed from runtime 2021-12-03 14:16:13 UTC
Red Hat Product Errata RHBA-2021:5003 0 None None None 2021-12-13 12:06:38 UTC

Description Douglas Smith 2021-10-27 15:51:08 UTC 
From upstream PR: https://github.com/k8snetworkplumbingwg/multus-cni/pull/742

"If the runtime passes a pod UID via K8S_POD_UID (which both CRIO and
containerd do as of mid-2021) then fail if the pod we get from the
Kube API has a different UID. This would indicate that the pod was
deleted and recreated while Multus was attempting to set up
networking for the old pod instance's sandbox, and it's pointless
to continue setting up a sandbox for a dead pod instance."
Comment 4 Weibin Liang 2021-12-08 16:41:40 UTC 
Follow the testing steps from https://bugzilla.redhat.com/show_bug.cgi?id=2017882

Testing passed in 4.9.0-0.nightly-2021-12-08-041936
Comment 6 errata-xmlrpc 2021-12-13 12:06:24 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 (OpenShift Container Platform 4.9.11 bug fix 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/RHBA-2021:5003
Note You need to log in before you can comment on or make changes to this bug.