Verified this bug on 4.3.0-0.nightly-2019-11-26-171052 the default description is: description: | # SR-IOV Network Operator for Openshift ## Introdution The sriov-network-operator is generally responsible for configuring the sriov components in a openshift cluster. ### Supported Features * Initialize the SR-IOV NICs on nodes. * provision SR-IOV device plugin on selected node. * provision SR-IOV CNI plugin on selected nodes. * manage configuration of SR-IOV device plugin. * generate net-att-def CRs for SR-IOV CNI plugin. This operator has to run in namespace 'openshift-sriov-network-operator'. An Operator Group is also required to install this operator: ``` $ oc create -f - <<EOF apiVersion: v1 kind: Namespace metadata: name: openshift-sriov-network-operator labels: openshift.io/run-level: "1" EOF $ oc create -f - <<EOF apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: sriov-network-operators namespace: openshift-sriov-network-operator spec: targetNamespaces: - openshift-sriov-network-operator EOF ``` displayName: SR-IOV Network Operator installModes: - supported: true type: OwnNamespace - supported: true type: SingleNamespace - supported: false type: MultiNamespace - supported: false type: AllNamespaces provider: name: Red Hat, Inc. version: 4.3.0-201911261117 name: "4.3" defaultChannel: "4.3" packageName: sriov-network-operator provider:
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:0062