Bug 1800426

Summary: [sriov] the SR-IOV device and CNI plugin pods are stuck in 'Terminating' state for a long time.
Product: OpenShift Container Platform Reporter: Peng Liu <pliu>
Component: NetworkingAssignee: Peng Liu <pliu>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-13 21:57:10 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 Peng Liu 2020-02-07 03:05:33 UTC 
Description of problem:
The SR-IOV device and CNI plugin pods are stuck in 'Terminating' state after the last user-defined SriovNetworkNodePolicy CR is deleted. It doesn't always happen.


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


How reproducible:


Steps to Reproduce:
1. Deploy the operator
2. Apply a SriovNetworkNodePolicy CR and wait until the node sync state becomes 'Succeeded'
3. Delete the SriovNetworkNodePolicy CR

Actual results:
The SR-IOV device and CNI plugin pods are stuck in 'Terminating' state for more than 5 mins.

Expected results:
The SR-IOV device and CNI plugin pods can be removed in 1 min.

Additional info:
Comment 2 zhaozhanqi 2020-02-11 06:49:45 UTC 
Verified this bug with image
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.4.0-202002101346-ose-sriov-network-webhook
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.4.0-202002101346-ose-sriov-network-operator
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.4.0-202002101346-ose-sriov-network-config-daemon

this issue did not be reproduced.
Comment 4 errata-xmlrpc 2020-05-13 21:57:10 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, 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-2020:0581