Bug 1960574

Summary: Managed cluster should ensure SR-IOV pods components have system-* priority class associated
Product: OpenShift Container Platform Reporter: Tinashe Chipomho <tchipomh>
Component: NetworkingAssignee: zenghui.shi <zshi>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium    
Version: 4.8   
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:31:06 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 Tinashe Chipomho 2021-05-14 09:27:56 UTC 
Description of problem:
Running conformance tests on ocp4.8 with RAN DU profile results in pods found with invalid tolerations:

Version-Release number of selected component (if applicable):
Client Version: 4.7.0-0.okd-2021-04-24-103438
Server Version: 4.8.0-fc.3
Kubernetes Version: v1.21.0-rc.0+291e731


How reproducible:
Run origin-tests against a dual-stack(v4/v6) enabled cluster. 


Steps to Reproduce:
1. Git clone https://github.com/openshift/origin.git into the test environment or 
 Extract the binaries - oc image extract {{ ocp_tests_image }} --path 
 /usr/bin/openshift-tests:
2. Navigate to the root directory and run “make” to generate the binaries
3. Run tests like - ./openshift-tests run {{ ocp_test_suite }} --junit-dir . --output-file ocp-test-suite.log

Actual results:
fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: May 12 17:29:43.407:
pods found with invalid tolerations:

openshift-sriov-network-operator/network-resources-injector-g49xx
openshift-sriov-network-operator/network-resources-injector-hrmwc
openshift-sriov-network-operator/network-resources-injector-m446l
openshift-sriov-network-operator/operator-webhook-57l2n
openshift-sriov-network-operator/operator-webhook-5n4cj
openshift-sriov-network-operator/operator-webhook-qn7w7
openshift-sriov-network-operator/sriov-cni-6h4m8
openshift-sriov-network-operator/sriov-cni-tc2b7
openshift-sriov-network-operator/sriov-device-plugin-4r8jm
openshift-sriov-network-operator/sriov-device-plugin-jgrc9
openshift-sriov-network-operator/sriov-network-config-daemon-8h6w9
openshift-sriov-network-operator/sriov-network-config-daemon-q4b9b
openshift-sriov-network-operator/sriov-network-operator-646474877-wt2xx

Expected results:
[sig-arch] Managed cluster should ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel] should pass

[It] ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel]
  github.com/openshift/origin/test/extended/pods/priorityclasses.go:20

When you run 
"oc get pods network-resources-injector-g49xx -n openshift-sriov-network-operator -o json | jq .spec.priorityClassName " the result is "null"


Additional info:
Comment 1 zenghui.shi 2021-05-18 03:32:10 UTC 
upstream PR: https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/128
Comment 3 zhaozhanqi 2021-07-14 04:22:11 UTC 
Verified this bug on 4.9.0-202107090514
Comment 6 errata-xmlrpc 2021-10-18 17:31:06 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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/RHSA-2021:3759