Description of problem: Hi, It's a minor issue with a minor change. If possible, rename the operator-webhook-config to sriov-operator-webhook-config ~~~ [root@openshift-jumpserver-0 sriovpod]# oc project default Now using project "default" on server "https://api.cluster.example.com:6443". [root@openshift-jumpserver-0 sriovpod]# oc get ValidatingWebhookConfiguration NAME WEBHOOKS AGE autoscaling.openshift.io 2 17h multus.openshift.io 1 17h operator-webhook-config 1 25m ~~~ operator-webhook-config too generic of a name for a resource that is cluster scoped: ~~~ [root@openshift-jumpserver-0 sriovpod]# oc get -o yaml ValidatingWebhookConfiguration operator-webhook-config | grep -i name f:name: {} k:{"name":"operator-webhook.sriovnetwork.openshift.io"}: f:name: {} f:namespace: {} f:name: {} f:namespaceSelector: {} name: operator-webhook-config name: default name: operator-webhook-service namespace: openshift-sriov-network-operator name: operator-webhook.sriovnetwork.openshift.io namespaceSelector: {} ~~~ Thanks! Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified this bug on 4.7.0-202011110821.p0 oc get ValidatingWebhookConfiguration NAME WEBHOOKS AGE autoscaling.openshift.io 2 27d multus.openshift.io 1 27d prometheusrules.openshift.io 1 27d sriov-operator-webhook-config 1 9d
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.7.0 security, bug fix, and enhancement 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-2020:5633